From: Keith Seitz <keiths@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/MI testsuite] mi_run_to_main/mi_next/mi_step
Date: Tue, 10 Sep 2002 07:25:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0209100724580.1392-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <15741.22284.95937.520608@localhost.redhat.com>
On Mon, 9 Sep 2002, Elena Zannoni wrote:
> Hmmm how does this interact with the mi_next_to, etc, functions that
> were added back in November?
> the original patch was here:
> http://sources.redhat.com/ml/gdb-patches/2001-10/msg00336.html
The two pathways are completely independent, although they appear to
accomplish the same thing. The stop specification for mi_step/next_to is
more stringent, though.
This patch just fixes what is already in mi-support.exp, which doesn't
work at all. As an alternative, we could whack mi_step and mi_next (or I
we could even re-write those to use mi_step_to and mi_next_to, come to
think of it).
Keith
next prev parent reply other threads:[~2002-09-10 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 13:43 Keith Seitz
2002-09-09 19:22 ` Elena Zannoni
2002-09-10 7:25 ` Keith Seitz [this message]
2002-09-10 9:32 ` Keith Seitz
2002-09-10 14:58 ` Elena Zannoni
2002-09-10 15:08 ` Keith Seitz
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=Pine.LNX.4.44.0209100724580.1392-100000@valrhona.uglyboxes.com \
--to=keiths@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