On Mon, Jul 11, 2005 at 06:11:58PM -0700, Jason Molenda wrote: > Yeah, Devang didn't present what we're doing here on the debug side > too well. We're giving up a bit of information from within gdb -- > it won't know what constructors and destructors a class has defined > -- for a large savings in debug info (this can be over 20% of an > application's debug info when lots of templates are in heavy use). > > Because the FUN stabs are still present, gdb knows about the > constructors; it can step into them, it can set breakpoints on them. > > For most developers, this isn't a worthwhile tradeoff, but for a > certain class of appliations the stabs debug info is enormous and > this helps to ameloriate that by giving up a small bit of gdb > functionality. This won't be enabled by default even within Apple, > but it is a useful option to have available.
Thanks for the explanation. That makes more sense. Personally, if you're going to do this, I don't see why you're keeping debug info for methods; either ditch all artificial methods (including defaulted constructors but not manually specified constructors), or ditch all methods. -- Daniel Jacobowitz CodeSourcery, LLC