paoda
/
zba
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix: run more than just the CPU when stepping via gdb

This commit is contained in:
Rekai Nyangadzayi Musuka 2023-02-13 17:15:39 -06:00
parent 7e9a3efacc
commit 76b3b4f582
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/core/emu.zig
View File

@ -200,15 +200,18 @@ pub const EmuThing = struct {
const cpu = self.cpu; const cpu = self.cpu;
const sched = self.scheduler; const sched = self.scheduler;
// Is true when we have executed one (1) instruction
var did_step: bool = false;
// TODO: How can I make it easier to keep this in lock-step with runFrame? // TODO: How can I make it easier to keep this in lock-step with runFrame?
while (true) { while (!did_step) {
if (!cpu.stepDmaTransfer()) { if (!cpu.stepDmaTransfer()) {
if (cpu.isHalted()) { if (cpu.isHalted()) {
// Fast-forward to next Event // Fast-forward to next Event
sched.tick = sched.queue.peek().?.tick; sched.tick = sched.queue.peek().?.tick;
} else { } else {
cpu.step(); cpu.step();
break; // this function won't return until we've actually stepped once did_step = true;
} }
} }