Difference between revisions of "HowTo:Use Dr Watson"
(added some specifics from the program's GUI, still "untested" cause im tired and lazy) |
m (→See also: XP Pro docs) |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | When running | + | {{NAV_Manual | |
+ | | previous=[[HowTo:Use GDB|Use GDB]] | ||
+ | | up=[[HowTos]] | ||
+ | | next=[[HowTo:Compile Wings3d from CVS|Compile Wings3d from CVS]] | ||
+ | }} | ||
+ | ---- | ||
+ | {{attention}} | ||
+ | =Using Dr Watson with Vegastrike= | ||
+ | When running Vegastrike 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 13: | ||
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. | ||
Line 12: | Line 20: | ||
If you can add any more detail to this page, please edit it! Much of this is copied from the forums and '''untested'''. | If you can add any more detail to this page, please edit it! Much of this is copied from the forums and '''untested'''. | ||
+ | |||
+ | =See also= | ||
+ | *[http://support.microsoft.com/default.aspx?scid=kb;EN-US;308538 Microsoft Help and Support article on Dr. Watson] | ||
+ | *[http://support.microsoft.com/default.aspx?scid=188296 Microsoft Help and Support article on enabling and disabling Dr. Watson] | ||
+ | *[http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_overview.mspx Microsoft XP Pro Documentation on Dr. Watson] | ||
+ | |||
+ | ---- | ||
+ | {{NAV_Manual | | ||
+ | | previous=[[HowTo:Use GDB|Use GDB]] | ||
+ | | up=[[HowTos]] | ||
+ | | next=[[HowTo:Compile Wings3d from CVS|Compile Wings3d from CVS]] | ||
+ | }} | ||
+ | |||
+ | [[Category:HowTos|Use Dr Watson]] |
Latest revision as of 03:41, 31 January 2006
Use GDB | HowTos | Compile Wings3d from CVS |
Using Dr Watson with Vegastrike
When running Vegastrike 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.
See also
- Microsoft Help and Support article on Dr. Watson
- Microsoft Help and Support article on enabling and disabling Dr. Watson
- Microsoft XP Pro Documentation on Dr. Watson
Use GDB | HowTos | Compile Wings3d from CVS |