From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Make continuations per-thread.
Date: Fri, 02 May 2008 13:44:00 -0000 [thread overview]
Message-ID: <20080502134325.GB29202@caradoc.them.org> (raw)
In-Reply-To: <200805021730.33831.vladimir@codesourcery.com>
On Fri, May 02, 2008 at 05:30:32PM +0400, Vladimir Prus wrote:
> I think the sensible behaviour is the same as for "next" -- abort
> whatever the operation we were doing. This means that we have to wipe
> continuation inside 'proceed'. I can adjust the patch this way, but
> does it make sense to you?
It makes sense, but I'm wondering how much work it would be to do
better than that (for all-stop, I mean - clearly you're planning to
do better for non-stop). In the example in my last message, there's
a point where thread 1 is stopped in the middle of a finish. Info
threads could show "(finishing)". Should step / next clear that,
or should we be able to step a bit and then print the return value
when we get there?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-02 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 23:08 Vladimir Prus
2008-05-02 3:00 ` Daniel Jacobowitz
2008-05-02 11:34 ` Pedro Alves
2008-05-02 11:43 ` Pedro Alves
2008-05-02 11:51 ` Vladimir Prus
2008-05-02 13:24 ` Daniel Jacobowitz
2008-05-02 13:30 ` Vladimir Prus
2008-05-02 13:44 ` Daniel Jacobowitz [this message]
2008-05-02 15:33 ` Ulrich Weigand
2008-05-06 19:02 ` Pedro Alves
2008-05-02 13:51 ` Pedro Alves
2008-05-02 14:15 ` Vladimir Prus
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=20080502134325.GB29202@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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