|
Post by nyxojaele on Dec 18, 2009 8:29:53 GMT -5
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?
|
|
|
Post by Truth Unknown on Jan 12, 2010 4:52:21 GMT -5
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
New Member
Posts: 2
|
Post by Forte on Jan 20, 2010 15:02:13 GMT -5
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)
|
|
|
Post by nyxojaele on Jan 24, 2010 9:58:15 GMT -5
<Edit: Moved to feature requests board>
|
|
ghost
New Member
Posts: 3
|
Post by ghost on Feb 6, 2010 21:08:01 GMT -5
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.
|
|
|
Post by boksha on Feb 18, 2010 10:11:58 GMT -5
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
New Member
Posts: 2
|
Post by Forte on May 4, 2010 4:09:34 GMT -5
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?
|
|