Changes between Version 8 and Version 9 of Debugging

Timestamp:

Mar 9, 2014, 10:26:57 PM (10 years ago)

Author:

historic_bruno

Comment:

--

Debugging

@@ -36 +36 @@
 == Debugging Crashes and Assertion Failures ==
 
-A crash, generally speaking, is when the game ceases to run at some point. In some crashes, the process will stop running and can no longer be debugged (e.g. a segmentation fault on *nix), or it will enter a debug state and wait for user action. An "assertion failure" may also be referred to as a crash, and often leads to a crash if ignored, but they are simply conditions that have been programmed as necessary for the software to run correctly. As 0 A.D. is still in development, there are many possible assertion failures and crashes.
+A crash, generally speaking, is when the game encounters an error and ceases to run at some point. In some crashes, the process will stop running and can no longer be debugged (e.g. a segmentation fault on *nix), or it will enter a debug state and wait for user action. An "assertion failure" may also be referred to as a crash, and often leads to a crash if ignored, but they are simply conditions that have been programmed as necessary for the software to run correctly. As 0 A.D. is still in development, there are many possible assertion failures and crashes.
 
 You want two things to debug a crash: 1) steps to reproduce, and 2) a call stack (i.e. back trace).