Originally posted by: SystemAdmin
[anahana said:]
> Thanks for your reply, I did not modify the code, I just added extra nodes and visits to the corresponding data
> files. As for the pdp.cpp, it is complete. I tried the thing again using C++.Net 2003 instead of 2005 and it worked
> smoothly.
This is unexpected, you should be getting the same behavior using both compilers. Do you think you could post the modified data files ? BTW which version of CP are you using ?
CP 1.3; it contains Dispatcher 4.5, Scheduler 6.5, and Solver 6.5
Did you try adding the penalty costs ?
No, I did not.
> I have another question though, I'm trying to trace the code, but whenever I start the debugger, it automatically
> goes to the Disaasembly part of the code (and it shows the memory locations and stacks) instead of going
> through the code line by line; I keep the "Step Over" and "Step Out" options, but I never get to the codel lines.
> Any idea why this is happening?
The provided ILOG CP librairies have been compiled in Release mode. You cannot step into the libraries' code (that's why you get the Disassembly panel). However you should still be able to step into the example's code as long as you compiled it in Debug mode.
If I keep "setting out" of the Disassembly pabel, I reach a point where the DOS Prompt window appears, empty, and I can't do anything after that. Can you please tell me exactly what I should do to trace the code lines? Maybe I'm doing something wrong.
Regards,
#CPOptimizer#DecisionOptimization