From: Vladimir Prus <vladimir@codesourcery.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: Make -exec-run and -exec-until into 'real' MI commands
Date: Wed, 13 Jan 2010 15:00:00 -0000 [thread overview]
Message-ID: <201001131800.24884.vladimir@codesourcery.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC515E07ADC1@EUSAACMS0703.eamcs.ericsson.se>
On Wednesday 13 January 2010 16:44:06 Marc Khouzam wrote:
>
> > -----Original Message-----
> > From: gdb-patches-owner@sourceware.org
> > [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Vladimir Prus
> > Sent: Wednesday, January 13, 2010 8:29 AM
> > To: gdb-patches@sourceware.org
> > Subject: Make -exec-run and -exec-until into 'real' MI commands
> >
> >
> > At present, '-exec-run' and '-exec-until' are directly routed
> > to CLI, with very little MI intervention. I have tried to fix
> > that before, but there were backward compatibility concerns.
> >
> > While working on multiexec MI patches, I really needed to have
> > -exec-run handled in MI, so I've made another attempt, which
> > is attached. Comments?
> >
>
> I just skimmed to patch to see if there was FE impacts, which
> I gather there is not.
>
> I noticed a typo:
>
> error ("-exec-until must be invoked with a signle argument");
> ^^^
Thanks, fixed that locally.
- Volodya
next prev parent reply other threads:[~2010-01-13 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:29 Vladimir Prus
2010-01-13 13:44 ` Marc Khouzam
2010-01-13 15:00 ` Vladimir Prus [this message]
2010-01-13 20:10 ` Daniel Jacobowitz
2010-01-13 20:13 ` Vladimir Prus
2010-01-13 20:26 ` Daniel Jacobowitz
2010-01-14 4:46 ` Joel Brobecker
2010-02-22 14:24 ` Vladimir Prus
2010-02-25 17:25 ` Joel Brobecker
2010-02-22 14:23 ` Vladimir Prus
2010-02-24 7:34 ` Vladimir Prus
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=201001131800.24884.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.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