From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@kealia.com, jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: test that GDB tolerates bad #inclusion data
Date: Tue, 23 Sep 2003 18:03:00 -0000 [thread overview]
Message-ID: <200309231803.h8NI3b2c026041@duracef.shout.net> (raw)
Jim, we gotta feed you the gdb_test_multiple kool-aid.
See gdb1250.exp or float.exp or watchpoint.exp.
Also, could you avoid the dependency on gcc version by using
preprocessed ".i" files with the bad line numbers already in them?
Instead of / in addition to the tests with C source.
I will run this patch through my testbed with -g2 and -g3
(I do have -g3 capability, I just don't do it in the weeklies yet)
and will post results in an hour or two.
Michael C
next reply other threads:[~2003-09-23 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 18:03 Michael Elizabeth Chastain [this message]
2003-09-23 22:33 ` Jim Blandy
2003-09-24 18:13 ` Jim Blandy
2003-09-24 18:13 ` Jim Blandy
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=200309231803.h8NI3b2c026041@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@kealia.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