|Compling a large app with -g email@example.com (1995-04-04)|
|Re: Compling a large app with -g firstname.lastname@example.org (1995-04-12)|
|From:||email@example.com (Richard Brosseau)|
|Date:||Tue, 4 Apr 1995 16:02:10 GMT|
Ever since I started developing in UNIX (about 10 years ago) I've always
run into the problem of not being able to compile a large application
(all .c or .cpp files) with the -g option; something would invariably
blow up, be it the linker, the debugger, or the swap space.
Having ported a large app from SunOS to Windows NT 3.5, I found a debugging
option on the microsoft compilers that allow the debugging information
to be placed in what they call a debug database. This allows me to compile
all 1000+ files in full debug and to run the sucker with a very minimal
performance hit. Full symbolic debugging everywhere in the app.
My less fortunate co-workers, however, are still selectivly "touching"
files and recompling them with -g in order to not blow up the debugger
and/or swap space.
My question is: why in the past 10 years has no progress been made on the
UNIX side of debugging information? If I'm wrong in assuming this, whose
complier/linker/debugger will allow me to compile everything in debug mode?
The company that will allow this will surely make a bundle...
Return to the
Search the comp.compilers archives again.