20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
→Debugging Segfaults & Obtaining Backtraces
m (→Debugging Segfaults & Obtaining Backtraces: http://forum.flightgear.org/viewtopic.php?f=17&t=19670&hilit=backtrace+cxx&start=15#p181541) |
|||
| Line 159: | Line 159: | ||
=== Debugging Segfaults & Obtaining Backtraces === | === Debugging Segfaults & Obtaining Backtraces === | ||
{{Note|This section is currently Linux/gdb specific}} | {{Note|This section is currently Linux/gdb specific. Any help in updating it to become less platform/OS/debugger-specific would be greatly appreciated!}} | ||
A '''segfault''' is another word for "crash", it's a so called "segmentation fault", where the program is doing things that it wasn't designed to do, such as accessing invalid memory for example, so that the operating system will terminate the process because its behavior is no longer valid/correct. These '''segfaults''' will typically happen due to coding errors, either in FlightGear or one of its dependencies (libraries like SimGear, plib, OpenSceneGraph or OpenAL). | A '''segfault''' is another word for "crash", it's a so called "segmentation fault", where the program is doing things that it wasn't designed to do, such as accessing invalid memory for example, so that the operating system will terminate the process because its behavior is no longer valid/correct. These '''segfaults''' will typically happen due to coding errors, either in FlightGear or one of its dependencies (libraries like SimGear, plib, OpenSceneGraph or OpenAL). | ||