From: Bob Rossi <bob_rossi@cox.net>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: -stack-list-frames HIGH_FRAME changes
Date: Fri, 05 May 2006 15:46:00 -0000 [thread overview]
Message-ID: <20060505144843.GA10374@brasko.net> (raw)
In-Reply-To: <200605051838.20652.ghost@cs.msu.su>
> > Please don't add new tests to just mi2-stack.exp. I don't much care
> > whether mi2-stack.exp is updated or not, but when we finalize mi3 and
> > create mi3-* tests, they're going to be copied from mi-*. So it's
> > important that new tests go there also.
>
> So, what's the point of mi2 tests at all?
> In any case, there's revised patch:
The mi- tests are the "current" MI tests. The mi2- tests make sure that
gdb -i=mi2 work.
So, at some point in the future we will make mi- tests become mi3-, we
will still have mi2- and mi- will become the new "current" MI tests.
Bob Rossi
next prev parent reply other threads:[~2006-05-05 15:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 7:54 Vladimir Prus
2006-05-05 10:30 ` Eli Zaretskii
2006-05-05 13:51 ` Daniel Jacobowitz
2006-05-05 14:39 ` Vladimir Prus
2006-05-05 14:53 ` Daniel Jacobowitz
2006-05-05 19:20 ` Jim Blandy
2006-05-05 15:46 ` Bob Rossi [this message]
2006-05-05 14:52 ` Daniel Jacobowitz
2006-09-07 16:10 ` Daniel Jacobowitz
2006-09-07 16:41 ` Vladimir Prus
2006-05-05 21:13 ` Eli Zaretskii
2006-09-07 16:10 ` Vladimir Prus
2006-09-07 22:37 Nick Roberts
2006-09-07 23:10 ` Daniel Jacobowitz
2006-09-08 6:28 ` Vladimir Prus
2006-09-08 8:30 ` Nick Roberts
2006-09-08 8:39 ` Vladimir Prus
2006-09-08 14:33 ` Daniel Jacobowitz
2006-09-08 16:37 ` Eli Zaretskii
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=20060505144843.GA10374@brasko.net \
--to=bob_rossi@cox.net \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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