From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [commit] LynxOS: Resume the same thread when receiving a thread create/exit event.
Date: Mon, 17 Dec 2012 11:33:00 -0000 [thread overview]
Message-ID: <20121217113318.GA3273@adacore.com> (raw)
In-Reply-To: <1355743597-15380-1-git-send-email-brobecker@adacore.com>
> gdb/gdbserver/ChangeLog:
>
> * lynx-low.c (lynx_resume): Use the resume_info parameter
> to determine the ptid for the lynx_ptrace call, unless
> it is equal to minus_one_ptid, in which case we use the
> ptid of the current_inferior.
> (lynx_wait_1): After having received a thread create/exit
> event, resume the inferior's execution using the signaling
> thread's ptid, rather than the old ptid.
[...]
> Checked in.
Actually, the checkin failed, because it depends on:
[RFC/commit 3/3] Delete unused variable in lynx_resume
http://www.sourceware.org/ml/gdb-patches/2012-12/msg00544.html
Resolving the conflict due to the dependency feels like undoing
the patch. So I will wait before putting this one in.
--
Joel
next prev parent reply other threads:[~2012-12-17 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 11:26 Joel Brobecker
2012-12-17 11:33 ` Joel Brobecker [this message]
2013-01-04 20:59 ` Pedro Alves
2013-01-07 11:52 ` Joel Brobecker
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=20121217113318.GA3273@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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