From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>,
Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: [RFA] Make continuations per-thread.
Date: Fri, 02 May 2008 11:43:00 -0000 [thread overview]
Message-ID: <200805021242.47803.pedro@codesourcery.com> (raw)
In-Reply-To: <200805021234.12472.pedro@codesourcery.com>
A Friday 02 May 2008 12:34:11, Pedro Alves wrote:
> A Friday 02 May 2008 04:00:12, Daniel Jacobowitz wrote:
> > 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.
>
> That's true. Attached is what we have next on the non-stop
> series to fix that. I'm not thrilled by it, but there are intermediate
> context switches in handle_inferior_event that make it much uglier to try
> to not make it centralized. This is one of the things that gets much
> better looking when we switch completelly to always-a-thread, and
> get rid of context-switching. I'm introducing another variable, instead of
> using previous_inferior_ptid, which would be a good candidate, but I have
> other plans for it.
Err, it doesn't fix all issues you mentioned. I'll have to do a more than
this.
--
Pedro Alves
next prev parent reply other threads:[~2008-05-02 11: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 [this message]
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=200805021242.47803.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=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