Difference between revisions of "HowTo:Use Dr Watson"
(added some specifics from the program's GUI, still "untested" cause im tired and lazy) |
m |
||
| Line 1: | Line 1: | ||
| − | When running Vega Strike on Windows, getting a backtrace from the Dr. Watson utility can help debug crashes. To set up Dr Watson, we first need to change the type of log it dumps, and the location. | + | When running Vega Strike on Windows, getting a backtrace from the Dr. Watson utility can help debug crashes. To set up Dr. Watson, we first need to change the type of log it dumps, and the location. |
Launch Dr. Watson. The easiest way to do this is by opening the "Run" dialogue from the start menu and typing in | Launch Dr. Watson. The easiest way to do this is by opening the "Run" dialogue from the start menu and typing in | ||
| Line 5: | Line 5: | ||
Otherwise, it should be located in ''c:\windows\system32'' | Otherwise, it should be located in ''c:\windows\system32'' | ||
| − | Change the location of its output somewhere convenient, and set "Crash Dump Type" to Mini (which is human-readable). Of course, "Create Crash Dump File" must be checked off, | + | Change the location of its output somewhere convenient, and set "Crash Dump Type" to Mini (which is human-readable). Of course, "Create Crash Dump File" must be checked off, and enabling "Dump Symbol Table" and "Dump All Thread Contents" would probably be a good idea. |
Then you should get a log produced when Vegastrike crashes. Please submit this with your bug report. | Then you should get a log produced when Vegastrike crashes. Please submit this with your bug report. | ||
Revision as of 12:27, 26 March 2005
When running Vega Strike on Windows, getting a backtrace from the Dr. Watson utility can help debug crashes. To set up Dr. Watson, we first need to change the type of log it dumps, and the location.
Launch Dr. Watson. The easiest way to do this is by opening the "Run" dialogue from the start menu and typing in
drwtsn32
Otherwise, it should be located in c:\windows\system32
Change the location of its output somewhere convenient, and set "Crash Dump Type" to Mini (which is human-readable). Of course, "Create Crash Dump File" must be checked off, and enabling "Dump Symbol Table" and "Dump All Thread Contents" would probably be a good idea.
Then you should get a log produced when Vegastrike crashes. Please submit this with your bug report.
FIXME
If you can add any more detail to this page, please edit it! Much of this is copied from the forums and untested.
