PCSX2 Documentation/GNU Debugger Tips: Difference between revisions
Jump to navigation
Jump to search
PCSX2 Documentation/GNU Debugger Tips (view source)
Revision as of 20:27, 9 January 2015
, 9 January 2015→SIGSEGV/Segmentation fault
| Line 30: | Line 30: | ||
A program have a limited range of memory that it can access. When you try to read/write outside, the kernel generate an error named segmentation fault. It is a critical error and generally it just crash. It is a bit difficult on PCSX2 because recompiler use this mechanism for optimization. So segmentation fault inside recompiler are normal and expected. | A program have a limited range of memory that it can access. When you try to read/write outside, the kernel generate an error named segmentation fault. It is a critical error and generally it just crash. It is a bit difficult on PCSX2 because recompiler use this mechanism for optimization. So segmentation fault inside recompiler are normal and expected. | ||
You can control signal behavior with the handle command for example. | You can control signal behavior with the handle command for example. | ||
*don't stop on SIGSEGV: handle SIGSEGV nostop | *don't stop on SIGSEGV: <code>handle SIGSEGV nostop</code> | ||
==GDB basic gui== | ==GDB basic gui== | ||