From: Kevin Buettner <kevinb@redhat.com>
To: Jim Blandy <jimb@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] dwarf2read.c: Add complaint for out of bounds DW_AT_ranges attribute
Date: Mon, 15 Sep 2003 17:21:00 -0000 [thread overview]
Message-ID: <1030915172109.ZM23207@localhost.localdomain> (raw)
In-Reply-To: Jim Blandy <jimb@redhat.com> "Re: [RFA] dwarf2read.c: Add complaint for out of bounds DW_AT_ranges attribute" (Sep 13, 12:51pm)
On Sep 13, 12:51pm, Jim Blandy wrote:
> Looks good.
>
> Kevin Buettner <kevinb@redhat.com> writes:
>
> > This one's almost obvious...
> >
> > GDB for the FR-V target was segfaulting when issued the "maint
> > check-symtabs" command. Clearly this is an indication that something
> > is wrong with the toolchain elsewhere, but GDB should not segfault
> > when it encounters bad debug info.
> >
> > Okay?
> >
> > * dwarf2read.c (dwarf2_get_pc_bounds): Complain if offset
> > associated with DW_AT_ranges attribute is out of bounds.
Committed.
Kevin
prev parent reply other threads:[~2003-09-15 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 21:20 Kevin Buettner
2003-09-13 17:53 ` Jim Blandy
2003-09-15 17:21 ` Kevin Buettner [this message]
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=1030915172109.ZM23207@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
/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