Files
ppsspp/Core/HLE
Henrik RydgårdandClaude Opus 5 9b577b5f46 Show module.section+offset next to addresses in exception/stack-trace logs
Added KernelModuleAddressDescription() (Core/HLE/sceKernelModule.cpp),
which looks up which currently loaded module (and text/data/bss/segment
section within it) an address falls in, e.g. "EBOOT.BIN.text+1234".
Wired it into:

- Core_MemoryException/Core_ExecException/Core_BreakException
  (Core/Core.cpp), appended next to every address/pc/ra shown in their
  log lines.
- FormatStackTrace (Core/MemFault.cpp), appended per-frame next to the
  existing symbol description.

This makes crash/exception logs actionable even when there's no symbol
at the faulting address - you at least get which module and section
it's in, useful for reverse engineering unfamiliar code.

Verified live via headless: injected a MIPS break instruction at the
current PC (through Tools/wsdbg) and confirmed the log line changed from
"break instruction hit at 088040ac" to "break instruction hit at 088040ac
[sceDisplayWaitVblank Test.text+ac]".

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XDNwPPuidmNxQGRJxBuRL6
2026-07-27 23:44:14 +02:00
..
2025-07-22 17:48:20 +02:00
2026-01-19 17:56:30 +01:00
2025-07-22 17:48:20 +02:00
2025-07-22 17:48:20 +02:00
2025-07-22 17:48:20 +02:00
2025-04-03 14:13:50 +02:00
2025-08-06 17:44:54 +02:00
2026-01-18 23:40:13 +02:00
2025-07-20 19:30:35 +02:00
2025-07-20 19:30:35 +02:00
2025-04-15 11:18:53 +02:00
…
2025-12-30 20:31:06 +01:00
…
…
…
2026-07-16 15:03:20 +02:00
…
…
…
2025-04-14 22:27:51 +02:00
2025-03-05 17:02:46 +01:00
…
2025-07-20 19:32:05 +02:00
2025-07-20 19:32:05 +02:00
2025-02-14 09:50:55 -06:00
2026-07-18 11:57:56 +02:00
2026-06-13 17:12:16 +02:00
…
2025-01-05 19:14:15 +01:00
2026-07-27 23:44:06 +02:00
2025-04-03 14:13:50 +02:00
…
2025-05-27 17:48:23 +02:00
2025-02-04 11:53:22 -06:00
…
2026-07-27 14:58:59 +02:00