From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: MI: asynchronous operation details
Date: Tue, 22 Nov 2005 14:19:00 -0000 [thread overview]
Message-ID: <20051122141901.GA15858@nevyn.them.org> (raw)
In-Reply-To: <200511221711.58694.ghost@cs.msu.su>
On Tue, Nov 22, 2005 at 05:11:58PM +0300, Vladimir Prus wrote:
> Except for "interrupt", other occurences are for various flavours of "run" --
> continue/next/nexti/step/stepi/unti/finish. So, it still looks like
> "-exec-interrupt" is the only command that can be meaningfully issued while
> inferior is running.
Not a lot of work has been done on taking advantage of asynchronous
execution, since so few targets offer it today. There's going to be
more in the future, I think. It's important mostly as an
infrastructure change for the GDB internals.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-22 14:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 8:33 Vladimir Prus
2005-11-22 9:07 ` Konstantin Karganov
2005-11-22 12:07 ` Vladimir Prus
2005-11-22 12:13 ` Bob Rossi
2005-11-22 12:20 ` Vladimir Prus
2005-11-22 13:38 ` Bob Rossi
2005-11-22 13:49 ` Vladimir Prus
2005-11-22 14:00 ` Bob Rossi
2005-11-22 14:12 ` Vladimir Prus
2005-11-22 14:19 ` Daniel Jacobowitz [this message]
2005-11-22 20:39 ` Nick Roberts
[not found] ` <200511230931.50438.ghost@cs.msu.su>
2005-11-23 9:31 ` Nick Roberts
2005-11-22 20:04 ` Eli Zaretskii
2005-11-22 14:59 ` How can I unsubscribe? Gengis Toledo
2005-11-22 15:11 ` Daniel Jacobowitz
2005-11-22 15:02 ` Daniel Jacobowitz
2005-11-22 16:48 ` Christopher Faylor
2005-11-22 18:42 ` Dave Korn
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=20051122141901.GA15858@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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