From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 2/2] gdb/infrun: stop all threads if there exists a non-stop target
Date: Wed, 1 Apr 2020 19:35:56 +0000 [thread overview]
Message-ID: <SN6PR11MB28936900C5C3536D8EB12C6FC4C90@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <7068fda4-b8aa-616f-1751-593d8af2a85f@redhat.com>
On Wednesday, April 1, 2020 8:10 PM, Pedro Alves wrote:
> Hi Tankut,
>
> Thanks much for this, and I'm very sorry for the delay.
>
> This looks good to me, with minor comments below. Please push.
Thank you. Fixed and pushed as
53cccef118b gdb/infrun: stop all threads if there exists a non-stop target
a0714d305fb gdb: define convenience function 'exists_non_stop_target'
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2020-04-01 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 8:30 [PATCH 0/2] All threads not stopped when a process exits Tankut Baris Aktemur
2020-02-06 8:30 ` [PATCH 1/2] gdb: define convenience function 'exists_non_stop_target' Tankut Baris Aktemur
2020-02-06 8:30 ` [PATCH 2/2] gdb/infrun: stop all threads if there exists a non-stop target Tankut Baris Aktemur
2020-04-01 18:10 ` Pedro Alves
2020-04-01 19:35 ` Aktemur, Tankut Baris [this message]
2020-03-03 8:35 ` [PING][PATCH 0/2] All threads not stopped when a process exits Tankut Baris Aktemur
2020-03-17 13:02 ` [PING^2][PATCH " Tankut Baris Aktemur
2020-04-01 13:34 ` [PING^3][PATCH " Tankut Baris Aktemur
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=SN6PR11MB28936900C5C3536D8EB12C6FC4C90@SN6PR11MB2893.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).