This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: DWARF-related warnings in DJGPP build of GDB
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 15 Apr 2009 22:26:37 +0300
- Subject: Re: DWARF-related warnings in DJGPP build of GDB
- References: <834owqmdli.fsf@gnu.org> <20090415162242.GC7585@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Wed, 15 Apr 2009 09:22:42 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > During symbol reading, inner block not inside outer block in prompt_for_continue.
> > During symbol reading, inner block (0x61ab0-0x6b68b) not inside outer block (0x64c90-0x64d2f).
> > During symbol reading, Offset 174868 out of bounds for DW_AT_ranges attribute.
> >
> > Is this a GCC problem, a GDB problem, or something else? Should I be
> > worried? My GCC version is 3.4.3, in case that matters.
>
> What you can do is verify that the addresses are correctly read
> by GDB.
>
> You could try dumping the DWARF data if you have a tool that does that
> on your system.
What tools can do that? Is there a way of doing this with Binutils?
> Otherwise, you could check the assembly file where
> prompt_for_continue is defined, and see if blocks indeed have
> the correct relationship in terms of block addresses.
Hints or an example for how to do that will be highly appreciated.
> It could be the compiler emitting wrong debugging info, or the
> assembler/linker toolchain that screws up.
I will try to upgrade to newer Binutils and to GCC 3.4.4, and see if
that helps.
Thanks for the feedback.