Changes between Version 1 and Version 2 of ReportingErrors

Timestamp:

Mar 19, 2012, 7:05:59 PM (12 years ago)

Author:

historic_bruno

Comment:

links to attached images

ReportingErrors

@@ -18 +18 @@
 On Windows the game will display a Program Error window such as the following:
 
-(Continue / Suppress / Break / Exit)
+[[Image(Windows-Program-Error.png)]]
 
 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.
@@ -30 +30 @@
 On OS X a crashing app will produce a problem report, first you will see a window like this:
 
-(Ignore / Report... / Reopen)
+[[Image(OSX-Quit-Unexpectedly.png)]]
 
 Choose "Report..." to view the report data including call stack:
 
+[[Image(OSX-Problem-Report.png)]]
 
 Copy and paste the full contents of the log into your bug report. Don't send the report to Apple since there is probably nothing they can do about it.
@@ -41 +42 @@
 On Linux and other Unix-like OSes, sometimes you will see a message window like the following after a crash:
 
-(Continue / Suppress / Break / Debugger / Exit)
+[[Image(Ubuntu-Error-Message.png)]]
 
 or if run from the terminal you may see a call stack and the following options: