Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: DWARF-related warnings in DJGPP build of GDB
Date: Fri, 17 Apr 2009 09:40:00 -0000	[thread overview]
Message-ID: <83ocuvk497.fsf@gnu.org> (raw)
In-Reply-To: <834owqmdli.fsf@gnu.org>

> Date: Wed, 15 Apr 2009 13:10:49 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> During debugging with DJGPP build of GDB built out of Apr 10th
> snapshot, I sometimes see various warnings that seem to be related to
> DWARF2.  Examples:
> 
>   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.

Btw, I see warnings on GNU/Linux as well, with GCC 4.0.3 and Binutils
2.16.91:

  During symbol reading, incomplete CFI data; unspecified registers (e.g., rax) at 0x444d44.
  During symbol reading, DW_AT_type missing from DW_TAG_subrange_type.

This is when debugging a recent snapshot of GDB with itself.

Does anyone else see this?  Are the compiler and/or Binutils installed
on that system (fencepost.gnu.org) too old?


  parent reply	other threads:[~2009-04-17  9:40 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
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 [this message]
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=83ocuvk497.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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