Debugging LARGE applications
Andrew Venmore
Dear Abbey,
We have a large application (140000 lines build, +150 forms),
but our development has for some time slowed to a crawl due
to loss of most use of the debugger (Delphi 1.0). The compiler
almost always says "...no debug information..." on the breakpoint
line. Some of the units are fine, but we cannot fix a pattern.
Now, when we are tired of MessageBeeps and MessageDlgs, the
only solution is to strip down the "uses" clause units of the
dpr and main.pas till only the unit we are interested in
remains (commenting out hundreds of lines of other code too,
of course). Then the compiler seems to find space for debug
information for this unit.
My plea(s):
1: Can anyone tell me why the compiler is not able to
include debug information for ALL source in the build.
2: If there is some 64k limit somewhere, does this same
limitation exist in Delphi 2 (very important).
3: Does anyone have any tips on how to shuffle the uses
units so as to make sure that the unit you want has debug
information.
Signed: Suicidal
(aven...@bluesky.co.za)
Stefan Hoffmeister
On 29 May 1996 23:06:43 GMT, aven...@bluesky.co.za (Andrew Venmore)
wrote:
>Dear Abbey,
>
>We have a large application (140000 lines build, +150 forms),
>but our development has for some time slowed to a crawl due
>to loss of most use of the debugger (Delphi 1.0). The compiler
>almost always says "...no debug information..." on the breakpoint
>line. Some of the units are fine, but we cannot fix a pattern.
>My plea(s):
>3: Does anyone have any tips on how to shuffle the uses
>units so as to make sure that the unit you want has debug
>information.
Setting Debug options is a local switch. So if you include the
compiler options for debugging in each unit you can control for each
unit whether debug information is generated or not.
Ctrl-O O will give you the current compiler settings in the source.
Have you tried using Turbo Debugger (4.6 will do, comes with the RAD
pack)?
--
Stefan Hoffmeister (Stefan.Ho...@Uni-Passau.de)
University of Passau, Bavaria, Germany
Alexander Tarasul
| aven...@bluesky.co.za (Andrew Venmore) wrote in article
<4oila3$j...@hermes.is.co.za>...
|
| We have a large application (140000 lines build, +150 forms),
| but our development has for some time slowed to a crawl due
| to loss of most use of the debugger (Delphi 1.0). The compiler
| almost always says "...no debug information..." on the breakpoint
| line. Some of the units are fine, but we cannot fix a pattern.
|
| Now, when we are tired of MessageBeeps and MessageDlgs, the
| only solution is to strip down the "uses" clause units of the
| dpr and main.pas till only the unit we are interested in
| remains (commenting out hundreds of lines of other code too,
| of course). Then the compiler seems to find space for debug
| information for this unit.
The possible solution is including to unit, which you are interesting in,
compiler directives : D+,L+ (refer to help) and disabling debug
information
for all project.
Probably you should put this inctructions to include file that make you
easy
to recompile enable/disable this feature.
Mike Chapin
In article <4oila3$j...@hermes.is.co.za>,
>but our development has for some time slowed to a crawl due
>to loss of most use of the debugger (Delphi 1.0). The compiler
>almost always says "...no debug information..." on the breakpoint
>line. Some of the units are fine, but we cannot fix a pattern.
>
>Now, when we are tired of MessageBeeps and MessageDlgs, the
>only solution is to strip down the "uses" clause units of the
>dpr and main.pas till only the unit we are interested in
>remains (commenting out hundreds of lines of other code too,
>of course). Then the compiler seems to find space for debug
>information for this unit.
>
>1: Can anyone tell me why the compiler is not able to
>include debug information for ALL source in the build.
>2: If there is some 64k limit somewhere, does this same
>limitation exist in Delphi 2 (very important).
>units so as to make sure that the unit you want has debug
>information.
Which debugger are you using? For a large application you should be using the
stand-alone Turbo Debugger. Not only will it handle large projects, it has
many more options, such as tracing ASM code.
-----------------------------------------------
Mike Chapin
Powder River
mch...@vcn.com
http://www.vcn.com/server/netizens/mchapin/first.html
Gillette, WY
Not the end of the earth but you can see it from
there.
-----------------------------------------------
Andrew Venmore
In article <4op9f9$7...@news.tcd.net>, mch...@vcn.com (Mike Chapin) wrote:
>Which debugger are you using? For a large application you should be using the
>stand-alone Turbo Debugger. Not only will it handle large projects, it has
>many more options, such as tracing ASM code.
Well, the integrated debugger. Are you suggesting that it is unable to handle
large applications. Can delphi 2.0's?.
Thanks
aven...@bluesky.co.za (Andrew Venmore)
Andrew Venmore
>Stefan.Ho...@Uni-Passau.De (Stefan Hoffmeister) wrote
>Setting Debug options is a local switch. So if you include the
>compiler options for debugging in each unit you can control for each
>unit whether debug information is generated or not.
>Ctrl-O O will give you the current compiler settings in the source.
>>shl...@ripco.com (Alexander Tarasul) wrote
>>The possible solution is including to unit, which you are interesting in,
>>compiler directives : D+,L+ (refer to help) and disabling debug
>>information
>>for all project.
>>Probably you should put this inctructions to include file that make you
>>easy
>>to recompile enable/disable this feature.
I have tried this on previous occasions, but as a triple check I built
the project again with project options for debugging all off. Then I
included the line {$D+, $L+} as the first line of a unit I wanted to
debug. After a make and a build I still could not put a breakpoint.
Thanks. Any other ideas?
>Have you tried using Turbo Debugger (4.6 will do, comes with the RAD
>pack)?
I REALLY want to use the integrated debugger
Thanks
aven...@bluesky.co.za (Andrew Venmore)
Bengt Richter
Stefan.Ho...@Uni-Passau.De (Stefan Hoffmeister) wrote:
>On 29 May 1996 23:06:43 GMT, aven...@bluesky.co.za (Andrew Venmore)
>wrote:
>>Dear Abbey,
>>
>>We have a large application (140000 lines build, +150 forms),
>>but our development has for some time slowed to a crawl due
>>to loss of most use of the debugger (Delphi 1.0). The compiler
>>almost always says "...no debug information..." on the breakpoint
>>line. Some of the units are fine, but we cannot fix a pattern.
>>My plea(s):
>>3: Does anyone have any tips on how to shuffle the uses
>>units so as to make sure that the unit you want has debug
>>information.
>Setting Debug options is a local switch. So if you include the
>compiler options for debugging in each unit you can control for each
>unit whether debug information is generated or not.
>Ctrl-O O will give you the current compiler settings in the source.
>Have you tried using Turbo Debugger (4.6 will do, comes with the RAD
>pack)?
TDW 4.6 won't run on NT though :-( so for D2 you need
TD32 (comes with BC++5.0, and I believe, TASM32).
It *should* have come with D2 Developer, IMHO.
Regards,
Bengt Richter
John McClenning
bo...@accessone.com (Bengt Richter) wrote:
>>Have you tried using Turbo Debugger (4.6 will do, comes with the RAD
>>pack)?
>TDW 4.6 won't run on NT though :-( so for D2 you need
>TD32 (comes with BC++5.0, and I believe, TASM32).
>It *should* have come with D2 Developer, IMHO.
I agree. It should have at least come with the Developer and C/S
versions of D2
John