This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC, GDB v6 and -fomit-frame-pointer
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: Alex Hornby <alex at anvil dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 9 Oct 2003 12:36:08 +0200
- Subject: Re: GCC, GDB v6 and -fomit-frame-pointer
- References: <3F852DBA.30401@anvil.com> <20031009123259.GA31546@nevyn.them.org>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Oct 09, 2003 at 08:33:00AM -0400, Daniel Jacobowitz wrote:
> On Thu, Oct 09, 2003 at 10:43:22AM +0100, Alex Hornby wrote:
> >
> > Does the new DWARF2 call frame in gdb 6.0 support mean programs compiled
> > with GCC and -fomit-frame-pointer can now be debugged? That would be
> > great as -fomit-frame-pointer provides quite a performance boost on x86.
> >
> > Assuming this is possible, what GCC and binutils versions would be
> > needed to take advantage of this?
>
> In general yes. Backtraces should work. Ultra-accurate argument and
> local variable printing requires -fvar-tracking in GCC so it's a little
> flaky now, but unwinding should be fine.
>
> Anything recent. I think 3.2, 3.3 are fine.
Even without CFI info? With the exception of IA-64/AMD64, GCC doesn't
generate unwind info by default, only when -fasynchronous-unwind-tables.
Jakub