The IBM ILOG Solver Reference Manual documents the classes IlcTrace. Also in "Trace events", we go into greater detail about trace events. Right now, in the context of tracing from a debugger, we want to indicate that instances of both those classes can be useful.
When you are running a Solver program from a debugger, and using instances of the class IlcTrace to trace the modifications of constrained variables, you can execute the constraint propagation step by step. All trace member functions of IlcTrace call the function ilc_trace_stop_here. A breakpoint can be set for the function ilc_trace_stop_here to stop the program after each call to a trace member function of the class IlcTrace. You do that in this way if you are using dbx or gdb:
(dbx) stop in ilc_trace_stop_here
(gdb) break ilc_trace_stop_here
|
|
On some platforms, such as Windows NT® , for example, you must prefix an underscore to the name of the function, like this: _ilc_trace_stop_here.
PREVIOUS
NEXT