From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] bpstat_do_actions in one place
Date: Mon, 05 May 2008 13:10:00 -0000 [thread overview]
Message-ID: <200805051658.32272.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080505114824.GB22274@caradoc.them.org>
On Monday 05 May 2008 15:48:24 Daniel Jacobowitz wrote:
> On Mon, May 05, 2008 at 01:04:05PM +0400, Vladimir Prus wrote:
> > In fact, things will go bad. I've checked in the following version of the
> > patch that uses RETURN_MASK_ALL.
>
> RETURN_MASK_ALL is almost never a good idea. Quit will now not quit
> all the way back to a prompt. Is that really what we want either?
Well, this was the behaviour I though to be the most reasonable.
> For instance, a program running in a while (1) loop with a breakpoint
> set in it, and the breakpoint has a command that produces output, like
> backtrace. Quit will now resume the program and generate another
> backtrace, I think.
Yes, I think so; seems fine to me. Is there any documentation for how
'quit' should generally work, especially inside breakpoint commands?
- Volodya
next prev parent reply other threads:[~2008-05-05 12:58 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 [this message]
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
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=200805051658.32272.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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