20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
→Debugging Segfaults & Obtaining Backtraces
| Line 161: | Line 161: | ||
{{Note|This section is currently Linux/gdb specific}} | {{Note|This section is currently Linux/gdb specific}} | ||
A '''segfault''' is another word for "crash", it's a so called "segmentation fault". These will typically happen due to coding errors, either in FlightGear or one of its dependencies (libraries like SimGear, plib, OpenSceneGraph or OpenAL). In order to see what was going on when the crash occurred, you'll need to build a binary with debugging symbols enabled, usually this includes FlightGear and SimGear - and possibly even OSG (OpenSceneGraph, only if your crash happens inside rendering related code). | 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. These will typically happen due to coding errors, either in FlightGear or one of its dependencies (libraries like SimGear, plib, OpenSceneGraph or OpenAL). In order to see what was going on when the crash occurred, you'll need to build a binary with debugging symbols enabled, usually this includes FlightGear and SimGear - and possibly even OSG (OpenSceneGraph, only if your crash happens inside rendering related code). | ||
A so called '''backtrace''' is basically pretty much like a flight data recorder that is used to conduct a post-crash analysis. | A so called '''backtrace''' is basically pretty much like a flight data recorder that is used to conduct a post-crash analysis. | ||