[DUG] I broke the D2006 debugger

[John Bird]

The D2006 debugger will no longer stop on any breakpoints in some of my
units.....funnily the one that produces the hard to track runtime error I am
trying to fix (out of range error).
 
I can prove the code is being executed by putting in Showmessage statements
at which it nicely stops, or my own info window, which duly shows where the
program is, and other info,  but no matter how I mark the breakpoints it
will no longer stop at any of them in the unit.  When it hits the error I am
trying to debug, it offers to break, but the place where it stops seems to
be where I was last in the IDE, nowhere meaningful.  
 
Help I want the debugger breakpoints back - any suggestions !!!
(Please do not say reformat the disk and reinstall Windows)
 
It did this last week in another version of this unit (there are no compile
errors) and it took 3 days to find that problem (an uncreated stringlist).
 
An earlier symptom was I had one project that always stopped at one
breakpoint even if I deleted it, it would reappear next time I ran the
program.
 
Please tell me I won't have to hack the code so I can debug it in D5 (it has
Rave stuff in it so I have to remove much of the guts).
 

John 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ns3.123.co.nz/pipermail/delphi/attachments/20060213/d8c78f06/attachment.html