From: Nick Roberts <nickrob@snap.net.nz>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: "Vladimir Prus" <vladimir@codesourcery.com>, <gdb@sources.redhat.com>
Subject: RE: Re: MI *stopped event with CLI commands
Date: Mon, 12 Jan 2009 11:36:00 -0000 [thread overview]
Message-ID: <18795.10995.345746.155013@kahikatea.snap.net.nz> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEED@ecamlmw720.eamcs.ericsson.se>
> I could switch to async mode to solve this problem, but
> I'm hesitant to do so because it may have side-effects to
> DSF-GDB that I may not be aware of.
Also very few targets currently support async mode. Linux, remote, Dicos?
> Except for this bug,
> I'm not too sure on the advantages of async-mode for DSF-GDB.
Non-stop mode seems to require async-mode but I'm not sure why it doesn't
enable it automatically.
> So, if you feel this bug can be fixed, I will probably wait
> for the fix, instead of risking going to async-mode.
It's not really a bug because CLI execution commands have never generated full
MI output in synchronous mode. I think synchronous really means that control
stays with the interpreter that issues the execution command until *after*
execution has finished. So any MI output, in this case, is really faked
output.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2009-01-12 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 4:20 Marc Khouzam
2008-12-15 6:17 ` Nick Roberts
2008-12-15 6:46 ` Vladimir Prus
2008-12-18 3:30 ` Marc Khouzam
2008-12-18 6:17 ` Nick Roberts
2009-01-12 3:11 ` Marc Khouzam
2009-01-12 11:36 ` Nick Roberts [this message]
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=18795.10995.345746.155013@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sources.redhat.com \
--cc=marc.khouzam@ericsson.com \
--cc=vladimir@codesourcery.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