From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] bpstat_do_actions in one place
Date: Mon, 05 May 2008 20:57:00 -0000 [thread overview]
Message-ID: <20080505194130.GA20958@caradoc.them.org> (raw)
In-Reply-To: <u8wyofsng.fsf@gnu.org>
On Mon, May 05, 2008 at 10:38:27PM +0300, Eli Zaretskii wrote:
> So it "discards the remaining output". But this `q' is not a command,
> just a one-letter response (GDB doesn't care what follows the initial
> `q'), just like it's sibling <RET> isn't a command, so there's no
> reason to expect that it will have _any_ effect inside breakpoint
> commands, or in any other context where GDB expects a command. Am I
> missing something?
I wasn't worried about embedding the q in the breakpoint commands
list, but about what effect it has when the prompt is triggered by
a command in the breakpoint command list. Basically, how far up
the call stack is considered "the remaining output"? Since what
it actually does is abort the command, not just discard the output.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-05 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 19:08 Vladimir Prus
2008-05-02 2:58 ` Daniel Jacobowitz
2008-05-05 9:56 ` Vladimir Prus
2008-05-05 13:06 ` Daniel Jacobowitz
2008-05-05 13:10 ` Vladimir Prus
2008-05-05 14:12 ` Daniel Jacobowitz
2008-05-05 20:47 ` Eli Zaretskii
2008-05-05 20:47 ` Daniel Jacobowitz
2008-05-05 20:53 ` Eli Zaretskii
2008-05-05 20:57 ` Daniel Jacobowitz [this message]
2008-05-06 15:46 ` Eli Zaretskii
2008-05-06 15:47 ` Daniel Jacobowitz
2008-05-06 19:24 ` Eli Zaretskii
2008-05-06 20:04 ` Daniel Jacobowitz
2008-05-07 11:38 ` Eli Zaretskii
2008-05-07 19:50 ` Daniel Jacobowitz
2008-05-08 4:23 ` Eli Zaretskii
2008-05-08 5:46 ` Daniel Jacobowitz
2008-05-08 11:34 ` Eli Zaretskii
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=20080505194130.GA20958@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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