public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com
Subject: [PING^2][PATCH 0/2] All threads not stopped when a process exits
Date: Tue, 17 Mar 2020 14:02:57 +0100	[thread overview]
Message-ID: <1584450177-24089-1-git-send-email-tankut.baris.aktemur@intel.com> (raw)
In-Reply-To: <1580977799-4371-1-git-send-email-tankut.baris.aktemur@intel.com>

> This is a 2-part series that aims to fix the problem of all threads
> not being stopped when a process exits.  The problem is, if we are in
> all-stop mode with multiple inferiors, and an exit event is received
> from an inferior, target_mourn_inferior() unpushes the process target
> and leaves exec_ops as the top target of the current inferior.  This
> new top target is not non-stop.  Hence, stop_all_threads() is skipped.
> If there are other inferiors, they remain running instead of being
> stopped.

Kindly pinging for the patch at

  https://sourceware.org/ml/gdb-patches/2020-02/msg00122.html

Thanks
Baris


  parent reply	other threads:[~2020-03-17 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  8:30 [PATCH " 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
2020-02-06  8:30 ` [PATCH 1/2] gdb: define convenience function 'exists_non_stop_target' Tankut Baris Aktemur
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 ` Tankut Baris Aktemur [this message]
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=1584450177-24089-1-git-send-email-tankut.baris.aktemur@intel.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).