HowTo:Use Dr Watson - Revision history

Halleck: /* See also */ XP Pro docs

2006-01-31T02:41:43Z

‎See also: XP Pro docs

Halleck: /* See also */ another link

2006-01-31T02:39:09Z

‎See also: another link

Halleck: /* See also */ +l Microsoft Help and Support article

2006-01-31T02:37:26Z

‎See also: +l Microsoft Help and Support article

Pirx at 17:40, 28 May 2005

2005-05-28T17:40:05Z

202.50.187.13 at 20:29, 29 March 2005

2005-03-29T20:29:10Z

Halleck at 10:27, 26 March 2005

2005-03-26T10:27:27Z

Halleck: added some specifics from the program's GUI, still "untested" cause im tired and lazy

2005-03-26T10:24:06Z

added some specifics from the program's GUI, still "untested" cause im tired and lazy

Programmerandrew at 09:25, 26 March 2005

2005-03-26T09:25:30Z

Programmerandrew: Added initial instructions

2005-03-26T09:20:53Z

Added initial instructions

New page

Getting a backtrace from Dr Watson is very helpful in debugging crashes. To set up Dr Watson, we first need to change the type of log it dumps, and the location.

Launch Dr Watson, it should be in ''c:\windows\system32''

Change the location of its output somewhere convenient, and set it to create a mini-dump (the full dumps are not human readable, this is).

Then you should get a log produced when Vegastrike crashes. Please submit this with your bug report.

If you can add any more detail to this page, please edit it! This is copied from the forums and '''untested'''.

@@ Line 24: / Line 24: @@
 *[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]
 ----

@@ Line 23: / Line 23: @@
 =See also=
 *[http://support.microsoft.com/default.aspx?scid=kb;EN-US;308538 Microsoft Help and Support article on Dr. Watson]
 ----

← Older revision		Revision as of 02:37, 31 January 2006
Line 22:		Line 22:

	=See also=		=See also=
		+	*[http://support.microsoft.com/default.aspx?scid=kb;EN-US;308538 Microsoft Help and Support article on Dr. Watson]

	----		----

@@ Line 1: / Line 1: @@
 {{NAV_Manual |
 | previous=[[HowTo:Use GDB|Use GDB]]
-| up=[[HowTo]]
+| up=[[HowTos]]
 | next=[[HowTo:Compile Wings3d from CVS|Compile Wings3d from CVS]]
 }}
 ----
 {{attention}}
-=Using Dr Watson with VegaStrike=
+=Using Dr Watson with Vegastrike=
-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 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
@@ Line 26: / Line 26: @@
 {{NAV_Manual |
 | previous=[[HowTo:Use GDB|Use GDB]]
-| up=[[HowTo]]
+| up=[[HowTos]]
 | next=[[HowTo:Compile Wings3d from CVS|Compile Wings3d from CVS]]
 }}

← Older revision		Revision as of 20:29, 29 March 2005
Line 1:		Line 1:
		+	{{NAV_Manual \|
		+	\| previous=[[HowTo:Use GDB\|Use GDB]]
		+	\| up=[[HowTo]]
		+	\| next=[[HowTo:Compile Wings3d from CVS\|Compile Wings3d from CVS]]
		+	}}
		+	----
		+	{{attention}}
		+	=Using Dr Watson with VegaStrike=
	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.

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=
		+
		+	----
		+	{{NAV_Manual \|
		+	\| previous=[[HowTo:Use GDB\|Use GDB]]
		+	\| up=[[HowTo]]
		+	\| next=[[HowTo:Compile Wings3d from CVS\|Compile Wings3d from CVS]]
		+	}}

@@ 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
@@ Line 5: / Line 5: @@
 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, amd enabling "Dump Symbol Table" and "Dump All Thread Contents" would probably be a good idea.
+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.

@@ Line 1: / Line 1: @@
-Getting a backtrace from Dr Watson is very helpful in debugging 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, it should be in ''c:\windows\system32''
+Launch Dr. Watson. The easiest way to do this is by opening the "Run" dialogue from the start menu and typing in
-Change the location of its output somewhere convenient, and set it to create a mini-dump (the full dumps are not human readable, this is).
+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, amd 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.
@@ Line 9: / Line 11: @@
 {{Fixme}}
-If you can add any more detail to this page, please edit it!  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'''.

← Older revision		Revision as of 09:25, 26 March 2005
Line 6:		Line 6:

	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.
		+
		+	{{Fixme}}

	If you can add any more detail to this page, please edit it! This is copied from the forums and '''untested'''.		If you can add any more detail to this page, please edit it! This is copied from the forums and '''untested'''.