From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Fix MI/async testsuite
Date: Sun, 04 May 2008 17:37:00 -0000 [thread overview]
Message-ID: <20080504172234.GB18323@caradoc.them.org> (raw)
In-Reply-To: <20080504171430.GA18323@caradoc.them.org>
On Sun, May 04, 2008 at 01:14:30PM -0400, Daniel Jacobowitz wrote:
> Why should we print ^running before we are ready for more input?
>
> *running, yes, soon as the target starts running. But ^running is the
> result of the command and should show up when the command is done,
> shouldn't it?
Duh, this is because of sync mode, right? Anyway, it seems like "gdb
accepts input after -exec-continue" and "gdb uses *running instead of
^running" should have the same condition, to avoid this weird output.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-04 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 13:40 Vladimir Prus
2008-05-04 17:14 ` Daniel Jacobowitz
2008-05-04 17:22 ` Vladimir Prus
2008-05-04 17:29 ` Daniel Jacobowitz
2008-05-04 17:37 ` Daniel Jacobowitz [this message]
2008-05-04 19:02 ` Vladimir Prus
2008-05-04 20:05 ` Daniel Jacobowitz
2008-05-05 9:15 ` Vladimir Prus
2008-06-05 16:38 ` Daniel Jacobowitz
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=20080504172234.GB18323@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--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