Content originally posted in LPCWare by MikeSimmonds on Wed Apr 24 06:06:42 MST 2013
[FONT=Tahoma][SIZE=2][Win XP Pro/SP3 32 Bit]
It seems that the latest debugger is not keeping accurate track of its hardware
breakpoints?
On the screenshot, it is clear that no bp's are set, the hardware FPB has no
bp's enabled, but the debugger claims that no breakpoint resources are free.
Additional background:
I had a [I]single[/I] bp (at LoadModule). This was called 3 times and in each call I:
did 2 'run to line' followed by an F6 (step over 'bl' call) and continue.
I noticed that the memory view on the FPB registes showed all 6 bp registers active.
However, a single F5 (step into) cleared these in the memory view.
I then attempted to 'run to line' in a "C" file and the error depicted showed up.
I think the debugger is at fault, but I you say not so, how can we remove these
bp's that the IDE thinks it, presumably, has to insert during the 'continue' phase
so that a new run to line bp can be inserted?
NB: The forum has reduced the size of the attachment, but (in FireFox with an
addon) I can zoom the image enough to see the text. Ask if you need the original
jpg attached as a zip.
Regards, Mike
[/SIZE][/FONT]
