This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Modify gcc for use with gdb (issue5132047)
On Wed, Oct 5, 2011 at 11:27, Tom Tromey <tromey@redhat.com> wrote:
> Diego> I proposed extending #pragma GCC options to bracket these functions
> Diego> with -g0. ÂThis would help reduce the impact of debug info size.
>
> I think this is fixing the wrong component: it means making a
> one-size-fits-all decision in the gcc build, instead of just making the
> debugger be more flexible.
That's true.
> If you want to pursue the inline function approach, I suggest
> resurrecting this gdb patch:
>
> Â Âhttp://sourceware.org/bugzilla/show_bug.cgi?id=8287
> Â Âhttp://sourceware.org/ml/gdb-patches/2010-06/msg00417.html
>
> Then you could add the appropriate blacklisting commands to gcc's
> .gdbinit by default.
I think this could work. I'm not sure I like the idea of having to
specify all these blacklist commands, but I appreciate how it can make
debugging more flexible.
Is this patch stalled? the last I see is Justin's reply to review
feedback, but no indication of whether it will be accepted.
Richi, Jakub, Lawrence, would you be OK with this approach? IIUC,
this means we'd have to add a bunch of blacklist commands to
gcc/gdbinit.in.
This does ties us to gdb, but I don't think that's a problem.
How does this work with C++? Do the functions need to be specified
with their mangled names?
Diego.