From: Pedro Alves <palves@redhat.com>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v7 3/5] gdb/remote: do not delete a thread if it has a pending exit event
Date: Wed, 13 May 2020 15:20:29 +0100 [thread overview]
Message-ID: <25a07937-5488-97e3-b194-4030e585a806@redhat.com> (raw)
In-Reply-To: <SN6PR11MB2893F02D3C4FE88A99C1C0C8C4A60@SN6PR11MB2893.namprd11.prod.outlook.com>
On 5/4/20 4:33 PM, Aktemur, Tankut Baris via Gdb-patches wrote:
> On Monday, May 4, 2020 4:43 PM, Pedro Alves wrote:
>> Tankut,
>>
>> I'm trying to get back to this, and I would like to apply the whole
>> series locally, but I'm afraid that I'm having trouble piecing the
>> series together.
>> Do you have a public branch where you have all the patches in the series
>> applied? You could push it under users/ on sourceware.org for example.
>>
>> Thanks,
>> Pedro Alves
>
> Hi Pedro,
>
> It's available at
> https://github.com/barisaktemur/gdb/commits/thread-exit-in-stop-all-threads-v8
Thanks Tankut. I've been playing with this. I'm now convinced that the
approach to make sure that we don't delete the last thread is the best one.
I've been experimenting with it, and I think we're OK wrt the
TARGET_WAITKIND_NO_RESUMED code in infrun.c. I pointed at before.
I've poked at the multi-exit.exp testcase to make it spawn more than
two inferiors, to make sure we always hit the race window, even on slower
systems. I'm now looking at multi-kill.exp. I'll have something to
show soon.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2020-05-13 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1587563226.git.tankut.baris.aktemur@intel.com>
2020-04-22 15:00 ` Tankut Baris Aktemur
2020-05-04 14:43 ` Pedro Alves
2020-05-04 15:33 ` Aktemur, Tankut Baris
2020-05-13 14:20 ` Pedro Alves [this message]
2020-04-22 15:00 ` [PATCH v7 5/5] gdb/infrun: handle already-exited threads when attempting to stop Tankut Baris Aktemur
2020-04-22 16:07 ` Aktemur, Tankut Baris
2020-05-03 15:38 ` Aktemur, Tankut Baris
2020-05-13 21:15 ` Pedro Alves
2020-05-14 8:50 ` Aktemur, Tankut Baris
2020-05-14 11:32 ` Pedro Alves
2020-05-14 11:42 ` Aktemur, Tankut Baris
2020-05-14 11:25 ` Pedro Alves
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=25a07937-5488-97e3-b194-4030e585a806@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.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