When you have a debugging session started, as stated in the previous section, you can use the debugging facility in the IDE to monitor the execution, examine values, set break points, examine call stacks, step through program code, etc., as you would do in developing other programs. For detailed debugging techniques, you should consult the manuals of the IDEs. Some notes specific to the SansGUI environment follow:
Because the SansGUI program is a Release build, you will not be able to trace into the SansGUI program code.
If your simulator routine crashes with a run-time error, SansGUI will try to find out the reason of the crash and report the location to you.
When you find the function in question, set a break point in the function and run the simulation again. Please remember that the function is defined for the whole class of objects or parts; therefore, when you trace the execution, it will break at each and every object or part derived from the class. You may want to use Edit>Breakpoints... to set some conditions for the breakpoint.
You can use the name strings, cObjName and cCmpnName, in the SG_OBJ to identify at which object or part the execution is stopped.
|
|
SansGUI Modeling and Simulation Environment Version 1.2
Copyright © 2000-2003 ProtoDesign, Inc. All rights reserved.