[DUG] I broke the D2006 debugger
John Bird
johnkbird at paradise.net.nz
Tue Feb 14 12:46:35 NZDT 2006
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
>
More information about the Delphi
mailing list