From: Jim Blandy <jimb@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: carlton@kealia.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: test that GDB tolerates bad #inclusion data
Date: Wed, 24 Sep 2003 18:13:00 -0000 [thread overview]
Message-ID: <vt28yoeoze2.fsf@zenia.home> (raw)
In-Reply-To: <vt2d6dqozp9.fsf@zenia.home>
Jim Blandy <jimb@redhat.com> writes:
> I'm glad you asked me to revise this:
Oh, and re-doing it helped me realize that it's not a case of GDB
coping with bogus information from the compiler --- a correct test
program, with plausible macro debug info, could also trigger the bug.
Thus the test being renamed from 'badinc' to 'lineinc'.
next prev parent reply other threads:[~2003-09-24 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 18:03 Michael Elizabeth Chastain
2003-09-23 22:33 ` Jim Blandy
2003-09-24 18:13 ` Jim Blandy
2003-09-24 18:13 ` Jim Blandy [this message]
2003-09-24 22:26 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2003-09-24 3:42 Michael Elizabeth Chastain
2003-09-23 19:59 Michael Elizabeth Chastain
2003-09-23 16:13 Jim Blandy
[not found] ` <yf2he337a2e.fsf@hawaii.kealia.com>
2003-09-23 17:06 ` 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=vt28yoeoze2.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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