On Mon, Apr 23, 2007 at 11:28:06PM +1000, Hamish Moffatt <[EMAIL PROTECTED]> wrote: > On Mon, Apr 23, 2007 at 07:38:15AM +0200, Mike Hommey wrote: > > On Sun, Apr 22, 2007 at 08:26:38PM -0400, Joey Hess <[EMAIL PROTECTED]> > > wrote: > > > Mark Brown wrote: > > > > I'd be interested to see some numbers on the archive size impact - my > > > > experience with C++ suggests that the size inflation caused by debug > > > > symbols can be enormous. > > > > > > I don't know about C++, but for C it depends. For example, aalib is a > > > 102 kb library that compresses to 44kb. Its debug symbols are 234 kb and > > > compress to 65 kb. > > > > > > OTOH, people rarely need full debugging information for aalib, it's > > > probably plenty to see its functions in the backtrace, and not have line > > > number info (bear in mind that line number info includes effectively the > > > entire source code of the program). So it I build it with -g1, the > > > debug symbols size drops to 48 kb and compresses to 14 kb. > > > > Except that -g1 drops line numbers... > > Wasn't that Joey's point?
The point is that it's pretty useless to have a backtrace without line numbers. It would be interesting if there was an option similar to -g1, but that would keep the line numbers (without the burden of keeping the whole source code) Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
