From: Elena Zannoni <ezannoni@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/MI testsuite] Add mi_runto
Date: Tue, 10 Sep 2002 14:58:00 -0000 [thread overview]
Message-ID: <15742.27282.583778.995345@localhost.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209100749280.1392-100000@valrhona.uglyboxes.com>
Keith Seitz writes:
> On Tue, 10 Sep 2002, Elena Zannoni wrote:
>
> > Yes, please. Thanks. It will be easier to maintain if we have only one
> > copy of these functions.
>
> UGH. Now I remember why I did this... mi_run_to_helper expects an MI
> command to execute, either "exec-continue" or "exec-run". There is no way
> for us to know this if we are attempting to run the inferior for the first
> time (or re-run it). This is usually handled by mi_run_cmd, and that is
> the difference between these to functions. They are essentially the same,
> otherwise. The best I can do is put the mi_gdb_test for the stop in
> anohter proc, but I think that would just mess the code up even more.
> (mi_step and mi_next are okay, though).
>
> Of course, it's your call.
> Keith
>
Oh ok. mi_run_to executes an inferior that has already started.
While mi_runto starts it from scratch.
Could we rename mi_run_to to something like mi_execute_to instead?
It is used only in mi-var-cmd.exp.
And add your paragraph above in mi-support.exp as a comment?
Elena
next prev parent reply other threads:[~2002-09-10 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 6:35 Keith Seitz
2002-09-09 19:31 ` Elena Zannoni
2002-09-10 7:31 ` Keith Seitz
2002-09-10 7:42 ` Elena Zannoni
2002-09-10 7:49 ` Keith Seitz
2002-09-10 14:58 ` Elena Zannoni [this message]
2002-09-10 15:22 ` Keith Seitz
2002-09-10 15:25 ` Elena Zannoni
2002-09-10 15:30 ` 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=15742.27282.583778.995345@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@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