Debug info

From: Joshua Higgs (Josh_at_scanningsystems.com.au)
Date: 11/21/03 

Date: Fri, 21 Nov 2003 10:36:35 +1000

Good morning all

I have a relatively large application which comprises of one EXE (quite
small) and about 100 packages (.BPL files). About 30 of the packages are
ones which I wrote myself, the others are 3rd party components.

All third party components have been built with debug info, detail map
files, include TD32 debug info blah blah blah - Likewise for all of my
packages.

The vcl suite of packages however, cannot be re-built with debug info as we
all know.

I have great difficulty getting debug info to load sometimes (ie. no blue
dots, disabled breakpoints).

The solutions that I generally employ to get them back are as follows:

    1) Run the application with the current project being the EXE rather
than the BPL as the currently selected package in delphi and relying on the
Run/Parameters option to point to the correct exe.

    2) "Build-All" (of my packages)

    3) "Build-All" (of the 3rd party stuff, and then build-all of mine)

    4) Exit delphi and start again

    5) Exit all other applications in case memory is an issue (I have 1 gig
of ram on my dev machine)

    6) Reboot my computer

    7) Ensure there are no dcu conflicts, bpl conflicts etc.

These solutions generally stick, but sometimes nothing seems to get them
back except for the occasional fluke when it decides it is going to come
back.

Is there a way you can get delphi to tell you more details about why debug
info is not available?

Thanks

Josh

Relevant Pages

  • Re: Debug info
    ... > I have a relatively large application which comprises of one EXE (quite ... > The vcl suite of packages however, cannot be re-built with debug info as we ... > than the BPL as the currently selected package in delphi and relying on the ...
    (borland.public.delphi.ide)
  • Re: Package location for runtime executable
    ... I am guessing no, because as part of the exe startup, it ... > searches for the presence of all these bpl files, ... able to use any of the run-time-loaded packages' units in your program. ... There is one way to make a BPL file: Tell Delphi to compile a DPK file. ...
    (borland.public.delphi.language.objectpascal)
  • Re: Packages
    ... >to compile the packages in the EXE and use them as separate .BPL files ... This is why the EXE was getting smaller as this list got bigger. ... >they have the packages listed. ...
    (alt.comp.lang.borland-delphi)
  • Re: Packages
    ... Setting the Use Runtime packages options tells Delphi not ... to compile the packages in the EXE and use them as separate .BPL files ... This is why the EXE was getting smaller as this list got bigger. ...
    (alt.comp.lang.borland-delphi)
  • Remote Debugger and Packages
    ... I have the networking right and can connect to the remote debugger, but it complains that I do not have debugging info. ... I built a simple test application and discovered that without "build with runtime packages" the simple test application works with remote debugging (ie the debug info is found and I can set breakpoints etc). ...
    (borland.public.delphi.non-technical)