[DUG] I broke the D2006 debugger

[John Bird]

So any units compiled without debugger options turned on, or not on the
compiler search path (from Google) will not get these pretty blue dots.

It does raise a valid question - why does the IDE allow breakpoints to be
set when it already must know they will be ignored?

And how can you get some units getting enabled breakpoints and some not in a
project?

John

Blue dots represent lines that can be debugged. You can only set breakpoints
on lines with blue dots.

If your code and blue dots are out of sync, then you have a rogue DCU
somewhere. Note that some lines won't have blue dots that are normal. For
example a line with a exit statement on it will not have a blue dot.

On 2/14/06, John Bird <johnkbird at paradise.net.nz> wrote:
> I think I have solved it - there were some compiler options in the 
> source file of the main unit (but this was the unit that was executing 
> breakpoints ok so I don't think that was it....I deleted these - they 
> were from D5
> anyway) and deleted all the files like .res and .dcu and rebuilt
everything
> and rechecked project options and now it works.....yay I have a debugger
> back.
>
> So can someone kindly tell me what the blue dots signify apart from 
> being very pretty?  I can accept there is a sort of logic to "needing 
> blue dots before the red dots will work" - but what does this mean 
> behind the scenes?
>
> Thanks for the hint about the dots - it did show there was something 
> screwy with this project as all the other projects were working OK 
> when I checked them.
>
> John
>
>
>
> -----Original Message-----
> From: John Bird [mailto:johnkbird at paradise.net.nz]
> Sent: Tuesday, 14 February 2006 12:47 p.m.
> To: 'Jeremy North'; 'NZ Borland Developers Group - Delphi List'
> Subject: RE: [DUG] I broke the D2006 debugger
>
>
> Well that does add something to the puzzle - as in the whole project 
> only one unit shows the blue dots in the left, and that is the only 
> one where the debugger stops with breakpoints.  However I can alter 
> and recompile the offending unit(s) and the resulting program does 
> reflect the changes, with or without blue dots.
>
> I tried opening other projects and rebuilding and they all show the blue
> dots.   So lets rephrase the question - what is the difference between the
> appearance of the dcu and other altered features in the program (which 
> are
> working) and the blue dots and the debugger (which are not).
>
> Yes I have searched for other instances of the dcu files and have 
> found none.
>
> John
>
>
> -----Original Message-----
> From: Jeremy North [mailto:jeremy.north at gmail.com]
> Sent: Tuesday, 14 February 2006 11:16 a.m.
> To: johnkbird at paradise.net.nz; NZ Borland Developers Group - Delphi 
> List
> Subject: Re: [DUG] I broke the D2006 debugger
>
>
> Do you have Software Assurance John?
>
> This really isn't a good QC report because you haven't provided steps 
> to reproduce.
>
> Does the unit when breakpoints are not triggered get the Blue dots in 
> it. Do the blue dots appear in the correct locations. Add about 10 
> lines of whitespace in a function and see if the blue dots are still 
> lined up correctly with the code in your unit.
>
> You might have an old DCU on your path that the compiler is finding 
> before your modified unit. Have you done a system search for the unit 
> name to make sure it isn't elsewhere on the system.
>
> On 2/14/06, John Bird <johnkbird at paradise.net.nz> wrote:
> > I submitted this to BDN Quality Central Report #:  24858
> >
> > http://qc.borland.com/wc/qcmain.aspx?d=24858
> > (I presume this is the best place to go to)
> >
> > Any other suggestions welcome please - I am stuck!!
> >
> > John
> >
> >
> > Any Borland Techos reading this?
> >
> > I need help as I have lost already about 4 days trying to debug a 
> > complex routine.  There are no compile errors, it runs fine until it 
> > hits a range error somewhere (don't know where yet as I can't get 
> > any breakpoints to stop it in this unit).
> >
> > Hey the debugger does not work anymore!  Can someone suggest where 
> > further up the line I can submit this problem to? I am out for a 
> > while, later in the day I will resort to the D5 debugger.
> >
> >
> > _______________________________________________
> > Delphi mailing list
> > Delphi at ns3.123.co.nz http://ns3.123.co.nz/mailman/listinfo/delphi
> >
>
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz http://ns3.123.co.nz/mailman/listinfo/delphi
>