Re: Policy or best practices for debug packages?
On Mon, Jul 07, 2008 at 05:39:05PM -0400, Daniel Jacobowitz wrote:
> Sorry, but this is either someone's uncontributed gcc patches, or
> (more likely) hearsay. The difference between -g (same as -g2) and
> -g3 is whether .debug_macinfo is generated - debug info for C/C++
> preprocessor macros. It's off by default because the generated data
> is huge.
Do programs like gdb take advantage of the .debug_macinfo in a useful
way if it's there? (I guess I should try it and see how big the dbg
packages get, and how useful it is for me in practice.)