Using Execute Breakpoints in the debugger

[nyxojaele]

I've been using the debugger with limited success recently- my biggest hangup being that I can't seem to figure out how to successfully use execute breakpoints. It's difficult to go about all my debugging with only memory breakpoints;;

It would seem that no matter what situation I set an execute breakpoint in, the debugger still displays "illegal" over the ASM in the code view where my breakpoint should be, and when execution reaches that point, it doesn't break.

I've found a website that was doing a bit of a tutorial on using the pSX debugger, and it mentioned something about how the execute breakpoints are somewhat "unstable", and don't play well with savestates, but the author said he would explain why later, and never did so.

Can anybody shed some light on this for me?

[Truth Unknown]

I think I can ask pSX Author to revisit this, no promises since he's been busy lately with his work and life (but mostly work from what I can tell).

[Forte]

That would be really great.
The way it is now, execution breakpoints seem only to work when a memory breakpoint was already triggered and you set the ex bp a few lines after that (which is fairly useless since you can step over that far)

[nyxojaele]

<Edit: Moved to feature requests board>

[ghost]

Just my own experience here but I think that the 'illegal' opcode (4C444444) is placed there so that when the emulator reaches this specific opcode it knows that it has reached a break point. This I believe is faster than checking the value of ip against all the breakpoints you have enabled. Sorry that doesnt answer your entire question but perhaps it may have cleared up one part of it.

[boksha]

nyxojaele, any chance of posting a link to that site? I've had a look at the debugger and breakpoints, and memory breakpoints sound incredibly useful, but as it is I have very little experience with debuggers and breakpoints.

(edit: actually, already got it to work; still interested in that site though)

[Forte]

Could it be that the dynamic recompiler is the reason breakpoints on execution don't work? Is it possible to switch to full interpreter mode?