|
|
@ -129,10 +129,15 @@ After building, the binaries `yuzu` and `yuzu-cmd` (depending on your build opti
|
|
|
|
|
|
|
|
|
|
|
|
### Debugging
|
|
|
|
### Debugging
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. Enable CPU debugging
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
2. Disable both Host MMU emulation options
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
3. Run gdb
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
```bash
|
|
|
|
cd data
|
|
|
|
cd data
|
|
|
|
gdb ../build/bin/yuzu # Start GDB
|
|
|
|
gdb ../build/bin/yuzu # Start GDB
|
|
|
|
(gdb) handle SIGSEGV nostop # Disable SIGSEGV exceptions, which are used by yuzu for memory access
|
|
|
|
|
|
|
|
(gdb) run # Run yuzu under GDB
|
|
|
|
(gdb) run # Run yuzu under GDB
|
|
|
|
<crash>
|
|
|
|
<crash>
|
|
|
|
(gdb) bt # Print a backtrace of the entire callstack to see which codepath the crash occurred on
|
|
|
|
(gdb) bt # Print a backtrace of the entire callstack to see which codepath the crash occurred on
|
|
|
|