From 93d0a12bb5fd911a2962183c550c82ce9194faae Mon Sep 17 00:00:00 2001 From: liamwhite Date: Sat, 8 Jul 2023 00:52:48 -0400 Subject: [PATCH] running gdb with sigsegv ignored is not helpful --- Building-for-Linux.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Building-for-Linux.md b/Building-for-Linux.md index 170b7aa..bdc2d0a 100644 --- a/Building-for-Linux.md +++ b/Building-for-Linux.md @@ -129,10 +129,15 @@ After building, the binaries `yuzu` and `yuzu-cmd` (depending on your build opti ### Debugging +1. Enable CPU debugging + ![](https://raw.githubusercontent.com/flathub/org.yuzu_emu.yuzu/master/assets/yuzu-settings-2.png) +2. Disable both Host MMU emulation options + ![](https://raw.githubusercontent.com/flathub/org.yuzu_emu.yuzu/master/assets/yuzu-settings-1.png) +3. Run gdb + ```bash cd data 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) bt # Print a backtrace of the entire callstack to see which codepath the crash occurred on