mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-09-01 02:05:21 +02:00
Henrik RydgårdandClaude Sonnet 5
3edea91c8e
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