Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Make continuations per-thread.
Date: Fri, 02 May 2008 03:00:00 -0000	[thread overview]
Message-ID: <20080502030012.GB28580@caradoc.them.org> (raw)
In-Reply-To: <200804242045.39246.vladimir@codesourcery.com>

On Thu, Apr 24, 2008 at 07:45:38PM +0300, Vladimir Prus wrote:
> 
> Right now, continuations are global. This means that if we're doing
> 'finish' in one thread, then we cannot do 'finish' or anything that
> also uses continuations, in any other thread. This seems unnecessary
> limitation, and this patch makes continuations per-thread.
> 
> Further into non-stop series, it really allows me to do 'finish' or 'step'
> in several threads independently.
> 
> OK?

Could you explain why this is safe?  We will do continuations for the
thread which reports an event only.  So it seems like continuations
for other threads will linger in their struct thread.

For example, if we finish from one thread and hit a breakpoint in
another thread before the finish returns.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-05-02  3:00 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 [this message]
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
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=20080502030012.GB28580@caradoc.them.org \
    --to=drow@false.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