If you have a problem with the program, it is possible that we will ask you to generate a trace. Traces are reports of what the program was doing when you encouter the problem.
The first step is to open the trace interface. There's 3 way to do this:
•By clicking the "Trace Ctrl" button of the File/Debug group.
•Directly from the keyboard by typing both the "Ctrl" key and a number "1" to "9". The number you use will preset the trace level in the interface.
•Trough the "Debug Wnd" interface by clicking the "New Trace" button.
The Trace Interface (Started with "Ctrl-1" to "Ctrl-9" or the "New Trace" button in the debugging interface)
|
|
Text window |
Some feedbacks, like start and stop...
|
Modules |
You can restrict the trace to certain modules of the program. The choices are:Main All the modules that start and stop sliceO along with the main loopsClass All the modules that work with the classesConfig The configuration menu and its modulesCuda All Cuda modulesMenu The Main menu and its modulesMode The differnt modes DLLsSystem The system DLLsTool The different tools DLLsUndo The undo/redo operations and menusVR All VR modulesFct Members of the "Module_Structures" DLL.Gadget The program's gadgets (like the tag and brush selection tools) in the "Module_Tools" DLLLib All the internal libraries used by the program (Lib_*.dll)Util Un-used at this time
|
Functions |
You can restrict the trace to certain functions within the desired modules of the program. The choices are:Main All the functions that start and stop sliceO along with the main loopsCtrl All the functions that are used in the module's interfacesIma All the functions that display images to the screenClass All the diffent classesDraw All the functions that draw to the image windowResult All the functions that are associated with the "Results" toolsScript All the functions that read/write scriptsUpdate Inside each modules, tehre is an "Update" function that react to external changesVar All the functions that read/write to system variablesWork Any function in a module that do the actual computation for that moduleIPC The "Inter Process Communication" tools used to synchronyse the processesProc Window's "Proc" functions.
|
Trace Level |
You can also restrict the trace to certain "levels". The higher the trace level, the more detailed will be the trace. But higher level traces will generate huge trace files and will also slow down the program. User the higher levels when you start the trace close to the problem you have. For example if you have a problem when you click on the "Erosion" button of the Morpho mode, start sliceOmatic, load you image, go to the Morpho mode and start the trace just before you click on the "Erosion" button. Stop the trace immediately after your problem show up! On the other hand, if your problem is a crash of sliceOmatic, then you do not have to stop the trace, the crash did that for you.
|
Start |
Start the trace for the selected modules and functions at the selected trace level. The trace will be called "sliceOmatic_trace.dat" and it will be placed in your "Scratch" directory (by default, Documents/TomoVision)
|
Stop |
Stop the trace
|
Exit |
Exit the interface |