From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: gdb 5.3 versus gdb HEAD%200302015
Date: Mon, 17 Feb 2003 17:02:00 -0000 [thread overview]
Message-ID: <200302171702.h1HH2CC12641@duracef.shout.net> (raw)
> If you use a setup_kfail, won't it start showing up as a KPASS for all
> of us with fixed GCCs?
Argh. You are right. I'll have to go with send_gdb/gdb_expect.
I've never done that in an MI context before. Time to study the
mi_support.exp.
(I have an afternoon date so this is my last message until this evening).
Michael C
next reply other threads:[~2003-02-17 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 17:02 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 17:08 Michael Elizabeth Chastain
2003-02-17 17:13 ` David Carlton
2003-02-17 16:44 Michael Elizabeth Chastain
2003-02-17 16:50 ` Daniel Jacobowitz
2003-02-17 16:32 Michael Elizabeth Chastain
2003-02-17 16:35 ` Daniel Jacobowitz
2003-02-17 15:32 Michael Elizabeth Chastain
2003-02-17 15:39 ` Daniel Jacobowitz
2003-02-17 17:03 ` David Carlton
2003-02-18 14:59 ` Michal Ludvig
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=200302171702.h1HH2CC12641@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb@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