Re: Gcc options for improving debugging?

[Alex Bennee <kernel-hacker@bennee.com>]

On Wed, 2006-07-19 at 09:05 -0400, Daniel Jacobowitz wrote:
> On Wed, Jul 19, 2006 at 12:32:58PM +0100, Alex Bennee wrote:
> > An alternate approach is to compile with -O3 but turn off specific
> > optimisations which make life tricky for gdb. So far I have:
> > 
> > * -ggdb3  (obviously)
> 
> This doesn't really give you anything beyond -g.  The only difference
> is that it will allow you to expand macros, and make your object files
> huge.

I was wondering what the difference was between that and -g3. Thanks.

> 
> > * -fno-omit-frame-pointer (seems to help with finding some variables)
> > 
> > What else would you suggest? Would this be worth adding to section 4.1
> > of the manual "Compiling for debugging".
> 
> Beyond this there's not really much you can do.  If you need inlining,
> you're in trouble, because GDB does not (yet) have decent inlining
> support - but it's on the list of things to improve.

Is it the inlineing that's causing the variables to get optimised
away??? That's my biggest problem at the moment.

--
Alex, homepage: http://www.bennee.com/~alex/
The new Congressmen say they're going to turn the government around. I
hope I don't get run over again.