[DUG] I broke the D2006 debugger

[Allan, Samuel]

I might be tempted to search my hard drive to see where the dcus are
coming out. If you are re-building them, then they must be going
somewhere. I suspect that your problem is caused by the dcus going
somewhere stupid, and the debugger trying to use old or non-existant
dcus. We get this ourselves every so often, but I can't say for sure
it's the same deal with you.

-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On Behalf Of John Bird
Sent: Tuesday, February 14 2006 9:56 a.m.
To: 'NZ Borland Developers Group - Delphi List'
Subject: RE: [DUG] I broke the D2006 debugger


I am foxed by this......I deleted all the dcu's for the whole project,
and
library files from my own library.  It made no difference, the
breakpoints
still would not work.

And it is even a bit more mysterious---the dcu's did not reappear in the
unit output directory even once the program was rebuilt.  If I close the
program ("File/Close All") and reopen and recompile they do reappear in
the
unit output directory.  So what on earth is Delphi 2006 doing with the
dcu's? is it caching them in memory or more likely putting them
somewhere in
a temporary folder....but I can't find them under "Program Files" or
"Borland" or "Documents and Settings"

John


-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On
Behalf Of Phil Middlemiss
Sent: Tuesday, 14 February 2006 9:26 a.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] I broke the D2006 debugger


John, one thing that has sometimes worked for me in the past is to 
delete all the DCUs of my own libraries before rebuilding - not just for

the project, but also any library files you use (that you have the 
source in the build path for). I don't know why this has worked but it
has.

Phil.

John Bird wrote:
> If you mean the "Project/Build All Projects" option that was one of 
> the first things I tried....
>
> The only thing I can think of was last week when I had an exception 
> when running an earlier faulty version of the program it threw an 
> exception read of address 000000 (which turned out to be from an 
> uncreated stringlist) and I ticked the option to "ignore this 
> exception type" and it never stopped on that after that....I think I 
> found the option to turn the ignore off under 
> "tool/options/debugger/borland debuggers/language exceptions" ... But 
> that didn't change anything with ignored breakpoints...
>
> It will stop at breakpoints in other units, but not this one (which 
> calls rvSystem1.execute later on).
>
> The program has cruised effortlessly over 4 breakpoints - showing all 
> the progress messages in a nice little information form window I put 
> up in between each one to prove it does so....(not a modal window btw 
> - it shows where it is and closes after a second)
>
> I really liked the debugger while it worked.  It was one of the best 
> features of Delphi.
>
> It was such a relief from my old language having to write extra code 
> to show internal info to the screen or log files.  Now I am right back

> there.....
>
> John
>
> -----Original Message-----
> From: Matt Comb [mailto:matt at ferndigital.com]
> Sent: Monday, 13 February 2006 11:51 p.m.
> To: johnkbird at paradise.net.nz; NZ Borland Developers Group - Delphi
List
> Subject: Re: [DUG] I broke the D2006 debugger
>
>
> John, are you doing a build or just running the app ?
>
> I suggest doing a build if you are not.
>
>
>
> _______________________________________________
> 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