From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/stabs] fix failed assertion during replacement of undefined type
Date: Thu, 17 Apr 2008 00:19:00 -0000 [thread overview]
Message-ID: <20080416230934.GA6274@caradoc.them.org> (raw)
In-Reply-To: <20080403212947.GA24753@adacore.com>
On Thu, Apr 03, 2008 at 02:29:47PM -0700, Joel Brobecker wrote:
> The compiler ended up emitting the following debugging info for this
> type, which is incomplete:
>
> .stabs "pck__data_t:t(0,32)=B(0,33)=xepck__data_t:",128,0,3,0
I think we should simply refuse this. It's circular and obviously
broken. We have a reference to a named type and the reference is
clearly intended to be to a non-volatile type, so GDB blowing up is
not entirely unreasonable.
That said, as you know, I care very little about the pathological
cases in our stabs parser; since no one more knowledgeable has
stepped up to object, this seems fine to commit.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-16 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 21:59 Joel Brobecker
2008-04-17 0:19 ` Daniel Jacobowitz [this message]
2008-04-18 8:55 ` Joel Brobecker
2008-04-19 2:13 ` Joel Brobecker
2008-04-19 6:00 ` Daniel Jacobowitz
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=20080416230934.GA6274@caradoc.them.org \
--to=drow@false.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