From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: ezannoni@redhat.com
Subject: Re: RFA: tolerate bogus Dwarf macro info
Date: Mon, 26 Sep 2005 17:48:00 -0000 [thread overview]
Message-ID: <m37jd3vi0g.fsf@alligator.red-bean.com> (raw)
In-Reply-To: <20050926162836.GA6510@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 26 Sep 2005 12:28:36 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> It breaks at stdarg.h. Presumably this has something to do with
> #include_next; have you submitted a GCC bug report to go with this?
Not yet; that'll be next.
>> This failure is covered by the existing test suite, if the test
>> programs are compiled with the -g3 flag.
>
> But since no one really tests that way, it's effectively not covered.
> Could you add a manual test case to the existing DWARF unit tests,
> please?
Sure thing.
next prev parent reply other threads:[~2005-09-26 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 16:21 Jim Blandy
2005-09-26 16:29 ` Daniel Jacobowitz
2005-09-26 17:48 ` Jim Blandy [this message]
2005-09-26 22:59 ` Jim Blandy
2005-09-26 22:19 ` Jim Blandy
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=m37jd3vi0g.fsf@alligator.red-bean.com \
--to=jimb@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.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