User:Jcreer/SMS:Bug Trace: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
# Run the trace_clear.bat | # Run the trace_clear.bat | ||
#: This will remove the debug_xms_*.dbg files. | #: This will remove the debug_xms_*.dbg files. | ||
Once Aquaveo developers have the DebugLog.txt file, they will begin working on a solution. Be advised that solutions to bugs typically take 1–2 months to be resolved and may take much longer depending on the issue. | |||
Revision as of 15:14, 13 June 2018
When SMS appears to have bug, performing a trace can help the developers isolate the cause. Having a bug trace report significantly increase the speed in which issues with the software can be resolved.
To perform a bug trace, the following files are needed:
- smsTrace122.exe
- trace_configure.bat
- trace_clear.bat
Perform a bug trace by doing the following:
- Run the trace_configure.bat file.
- This will create two files (debug_xms_trace.dbg and debug_xms_log.dbg) in the C:\temp\ directory and delete the DebugLog.txt if it exists.
- copy the smsTraceFile to the where SMS is located on your machine. "C:\Program Files\SMS 12.3 64-bit"
- Run the smsTrace122.exe until finished tracing.
- Execute the SMS function that causes your issue.
- This should cause the crash/hang.
- Return the C:\temp\DebugLog.txt to Aquaveo tech support.
- This file contains the trace and may be viewed in an editor.
- Run the trace_clear.bat
- This will remove the debug_xms_*.dbg files.
Once Aquaveo developers have the DebugLog.txt file, they will begin working on a solution. Be advised that solutions to bugs typically take 1–2 months to be resolved and may take much longer depending on the issue.
