Debugger: track hit counts on address breakpoints, expose via cpu.breakpoint.list

BreakPoint (cpu.breakpoint.*) had no hit-count tracking at all, unlike
MemCheck (memory.breakpoint.*), which already tracks numHits. This made it
genuinely hard to tell "this breakpoint is never being reached" apart from
"it's being reached but I'm not seeing the log/pause where I'm looking" -
directly informed by repeatedly hitting exactly that ambiguity while
debugging the VSH boot path this session (see docs/VSHBootInvestigation.md).

Added BreakPoint::numHits, incremented in BreakpointManager::ExecBreakPoint()
whenever a breakpoint's address is hit and any condition passes (matching
MemCheck::Apply()'s existing semantics - counts real triggers, not just
"execution passed through here"). Exposed as a new "hits" field in
cpu.breakpoint.list's response.

Verified live via PPSSPPHeadless + wsdbg: hits reads 0 before the CPU
resumes, 1 after the breakpoint fires once. UnitTest.exe all: 49/49 passed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GZq8ZtJmFY7bkX5FVkr3P9
This commit is contained in:
Henrik Rydgård
2026-08-14 11:04:32 +02:00
co-authored by Claude Sonnet 5
parent 4389f706b9
commit 3edea91c8e
3 changed files with 12 additions and 1 deletions
+3 -1
View File
@@ -281,7 +281,7 @@ BreakAction BreakpointManager::ExecBreakPoint(u32 addr) {
return BREAK_ACTION_IGNORE;
size_t bp = FindBreakpoint(addr, false);
if (bp != INVALID_BREAKPOINT) {
const BreakPoint &info = breakPoints_[bp];
BreakPoint &info = breakPoints_[bp];
if (info.hasCond) {
// Evaluate the breakpoint and abort if necessary.
@@ -290,6 +290,8 @@ BreakAction BreakpointManager::ExecBreakPoint(u32 addr) {
return BREAK_ACTION_IGNORE;
}
++info.numHits;
if (info.result & BREAK_ACTION_LOG) {
if (info.logFormat.empty()) {
NOTICE_LOG(Log::JIT, "BKP PC=%08x (%s)", addr, g_symbolMap->GetDescription(addr).c_str());