From: Vladimir Prus <ghost@cs.msu.su>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: MI Development
Date: Wed, 05 Sep 2007 05:40:00 -0000 [thread overview]
Message-ID: <200709050940.18839.ghost@cs.msu.su> (raw)
In-Reply-To: <18142.16140.486009.379849@kahikatea.snap.net.nz>
On Wednesday 05 September 2007 09:30:52 Nick Roberts wrote:
> > CLI commands bypass MI When a CLI command is issued, we don't see
> > "^running". As result, frontend can easily think that gdb is waiting for
> > commands while inferior is running.
>
> With asynchronous operation, asynchronous CLI commands give the same MI output
> that MI commands do.
Why would I want to enable asynchronous operation for that to work? The
default behaviour is just broken, so even if --async fixes that, we should not
require any switches to get non-broken behaviour.
- Volodya
next prev parent reply other threads:[~2007-09-05 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 13:40 Vladimir Prus
[not found] ` <200709041628.15560.apoenitz@trolltech.com>
2007-09-04 15:06 ` Vladimir Prus
2007-09-05 5:31 ` Nick Roberts
2007-09-05 5:40 ` Vladimir Prus [this message]
2007-09-05 6:29 ` Nick Roberts
2007-09-05 6:33 ` Vladimir Prus
2007-09-05 6:43 ` Nick Roberts
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=200709050940.18839.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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