From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: DWARF-related warnings in DJGPP build of GDB
Date: Wed, 15 Apr 2009 19:26:00 -0000 [thread overview]
Message-ID: <83k55llnv6.fsf@gnu.org> (raw)
In-Reply-To: <20090415162242.GC7585@adacore.com>
> 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.
next prev parent reply other threads:[~2009-04-15 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 10:10 Eli Zaretskii
2009-04-15 16:22 ` Joel Brobecker
2009-04-15 19:26 ` Eli Zaretskii [this message]
2009-04-15 19:31 ` Pedro Alves
2009-04-15 20:48 ` Eli Zaretskii
2009-04-15 21:00 ` Pedro Alves
2009-04-15 19:48 ` Tom Tromey
2009-04-15 20:17 ` Eli Zaretskii
2009-04-15 22:29 ` Joel Brobecker
2009-04-17 9:40 ` Eli Zaretskii
2009-04-17 10:11 ` Mark Kettenis
2009-04-17 10:19 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k55llnv6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox