Changes between Version 3 and Version 4 of ReportingErrors

Timestamp:

Mar 19, 2012, 10:58:47 PM (12 years ago)

Author:

historic_bruno

Comment:

--

ReportingErrors

@@ -22 +22 @@
 and generate crashlog files in `%appdata%\0ad\logs\`. The crash dump contains a call stack, which is the state of the program at the time it crashed, this is the most useful info for troubleshooting. There is also a text file with errors that were logged and basic info on the user's system (OS, driver versions, CPU, etc.) Only the most recent crashlog is saved, so it's best to report the crash as soon as it occurs.
 
-Attach the crashlog files to your ticket. If you'd like to try debugging the error yourself, see DebuggingOnWindows.
+Attach the crashlog files to your bug report. If you'd like to try debugging the error yourself, see DebuggingOnWindows.
 
 If the game crashes early (before the main menu is displayed), it may not be able to create crashlog files or error logs. In this case it's useful to read the debug output from the game's startup which is normally not visible, using Microsoft's free [http://technet.microsoft.com/en-us/sysinternals/bb896647 DebugView] utility.
@@ -48 +48 @@
 `(C)ontinue, (S)uppress, (B)reak, Launch (D)ebugger, or (E)xit?`
 
-This call stack is generally not very useful as symbols are not loaded, so choose the "Debugger" option to open GDB. At the `(gdb)` prompt, type `bt full` to get the full call stack, then copy-and-paste that into your bug report.
+This call stack is generally not very useful as symbols are not loaded, so choose the "Debugger" option to open GDB. At the `(gdb)` prompt, type `thread apply all bt full` (for a trace of all threads, or `bt full` for only the crashing thread) to get the call stack, then copy-and-paste the results into your bug report.
 
-If you got a segfault instead and no debug options, you'll need to know how to reproduce the crash, then run the game in GDB:
+If you get a "Segmentation fault" instead and no debug options, you'll need to know how to reproduce the crash, then run the game in GDB:
 {{{
 cd binaries/system
@@ -56 +56 @@
 (gdb) run
 ... crash!
-(gdb) bt full
+(gdb) thread apply all bt full
 }}}
 
@@ -63 +63 @@
 An error is when the game notifies the user that something bad happened, they are typically both logged and displayed as messages in the game window:
 
+[[Image(ErrorAndWarning.png)]]
 
-
-The game will continue after most errors, but they may trigger more errors. Errors are often caught by the developers but sometimes they sneak into the Alpha releases. To report the exact messages, open interestinglog.html in your web browser and copy the contents into your bug report. The location of the logs varies by OS:
+The game will continue after most errors, but they may trigger more errors. Errors are often caught by the developers but sometimes they sneak into the Alpha releases. To report the exact messages, open `interestinglog.html` in your web browser and copy the contents into your bug report. The location of the logs varies by OS:
  * Windows: `%appdata%\0ad\logs\`
  * Linux: `~/.config/0ad/logs/`