From: Vladimir Prus <ghost@cs.msu.su>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: MI: output of -break-insert and -break-watch
Date: Fri, 17 Feb 2006 14:03:00 -0000 [thread overview]
Message-ID: <200602171702.59498.ghost@cs.msu.su> (raw)
In-Reply-To: <uu0aygkgq.fsf@gnu.org>
On Friday 17 February 2006 16:53, Eli Zaretskii wrote:
> > From: Vladimir Prus <ghost@cs.msu.su>
> > Date: Fri, 17 Feb 2006 15:37:21 +0300
> >
> > The output of -break-insert and -break-watch currently looks like this:
> >
> > ^done,bkpt={number="1",......
> >
> > and
> >
> > ^done,wpt={number="2",.......
> >
> > What is exactly the point of using different field names: "bkpt" and
> > "wpt"? This makes it impossible to get the number of set breakpoint in a
> > uniform fashion -- I need to have some conditional on the type of
> > breakpoint, or add logic that checks if "bkpt" or "wpt" is present in
> > reply.
> >
> > Why can't we have just:
> >
> > ^done,number="1"
> >
> > ? And this can be done in backward-compatible way, btw.
>
> How about
>
> ^done,type="wpt",number="2"...
>
> or
> ^done,bkpt={number="2",type="wpt",...
>
> instead?
That is, with added "type" field? No objections from me.
> I think leaving the breakpoint type out might not be a good idea,
> since the response might not come in sync with the commands. That is,
> you could have sent several commands before you get the first
> response. In that case, you will not easily know which response is
> for what command.
I'm not sure about this. If your really want to send several command, there
are two mechanisms:
1. You can use the "token" in original MI command, which will be returne in
reply.
2. You can just send the commands anyway, and keep a list of commands for
which there's no reply. I believe that the order of replies and commands is
the same, so it's easy to match replies with commands.
Anyway, extra "type" field won't hurt much.
- Volodya
next prev parent reply other threads:[~2006-02-17 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 12:37 Vladimir Prus
2006-02-17 13:53 ` Eli Zaretskii
2006-02-17 14:03 ` Vladimir Prus [this message]
2006-02-17 13:56 ` Daniel Jacobowitz
2006-02-17 14:14 ` Vladimir Prus
2006-02-17 14:24 ` Daniel Jacobowitz
2006-02-17 14:18 ` Daniel Jacobowitz
2006-02-17 15:00 ` 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=200602171702.59498.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=eliz@gnu.org \
--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