From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: nickrob@snap.net.nz, gdb@sources.redhat.com
Subject: Re: MI: "^running" issues
Date: Wed, 05 Sep 2007 17:27:00 -0000 [thread overview]
Message-ID: <uodght43u.fsf@gnu.org> (raw)
In-Reply-To: <200709050938.45290.ghost@cs.msu.su> (message from Vladimir Prus on Wed, 5 Sep 2007 09:38:45 +0400)
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Wed, 5 Sep 2007 09:38:45 +0400
> Cc: gdb@sources.redhat.com
>
> > > - Killing the idea of async commands. It does not seem to be very useful
> > > at this point, so we might be better off ripping it and implementing afresh
> > > later, when it's understood what they should be.
> >
> > I'm working in the opposite direction: trying to get GDB to work asynchronously.
> > I don't see the point of ripping out what is already there.
>
> Then, can you please provide a specification of what "asynchronously" means, and
> why it's good for users and frontends?
Asynchronous execution means that some GDB commands can be run while
GDB waits for the target to stop. It is good for users because you
can do something useful while you wait for the target to stop.
next prev parent reply other threads:[~2007-09-05 17:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 12:53 Vladimir Prus
2007-09-05 5:24 ` Nick Roberts
2007-09-05 5:39 ` Vladimir Prus
2007-09-05 6:25 ` Nick Roberts
2007-09-05 17:27 ` Eli Zaretskii [this message]
2007-09-05 18:42 ` Vladimir Prus
2007-09-06 6:46 ` Eli Zaretskii
2007-09-06 7:20 ` Vladimir Prus
2007-09-06 8:12 ` Fabian Cenedese
2007-09-06 8:24 ` Mark Kettenis
2007-09-06 11:39 ` Nick Roberts
2007-09-06 21:18 ` Vladimir Prus
2007-09-06 14:38 ` Bob Rossi
2007-09-06 15:06 ` Vladimir Prus
2007-09-06 19:34 ` Eli Zaretskii
2007-09-06 19:38 ` Vladimir Prus
2007-09-07 9:04 ` Eli Zaretskii
2007-09-07 9:15 ` Nick Roberts
2007-09-07 10:59 ` Vladimir Prus
2007-09-07 18:06 ` Eli Zaretskii
2007-09-07 18:18 ` Daniel Jacobowitz
2007-09-07 18:24 ` Eli Zaretskii
2007-09-08 0:30 ` Daniel Jacobowitz
2007-09-08 3:45 ` Nick Roberts
2007-09-08 7:21 ` Daniel Jacobowitz
2007-09-09 20:10 ` Nick Roberts
2007-09-07 8:11 ` Nick Roberts
2007-09-06 15:03 ` Jim Blandy
2007-09-06 18:08 ` Jim Ingham
2007-09-06 18:34 ` Vladimir Prus
2007-09-06 18:41 ` Jim Ingham
2007-09-06 18:48 ` Vladimir Prus
2007-09-07 5:54 ` André Pönitz
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=uodght43u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
--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