From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 0/3] Querying registers of already-exited processes
Date: Fri, 4 Dec 2020 11:36:07 +0000 [thread overview]
Message-ID: <SN6PR11MB28935A8A852B57CBDB20A993C4F10@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <cover.1605286391.git.tankut.baris.aktemur@intel.com>
Ping.
Thanks
-Baris
On Friday, November 13, 2020 5:57 PM, Aktemur, Tankut Baris wrote:
> Hello,
>
> This series can be considered a continuation of
>
> commit 4778a5f87d253399083565b4919816f541ebe414
> Author: Tom de Vries <tdevries@suse.de>
> Date: Tue Apr 21 15:45:57 2020 +0200
>
> [gdb] Fix hang after ext sigkill
>
> and
>
> commit 47f1aceffa02be4726b854082d7587eb259136e0
> Author: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
> Date: Thu May 14 13:59:54 2020 +0200
>
> gdb/infrun: handle already-exited threads when attempting to stop
>
> The starting point was PR gdb/26877:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26877
>
> The first two patches are preparatory. The main patch is the last one.
>
> Regards
> Baris
>
>
> Tankut Baris Aktemur (3):
> gdb/testsuite: update the expected output in
> gdb.threads/killed-outside.exp
> gdb/regcache: return REG_UNAVAILABLE if raw_update raises
> NOT_AVAILABLE_ERROR
> gdb: raise and handle NOT_AVAILABLE_ERROR when accessing frame PC
>
> gdb/amd64-linux-nat.c | 3 +-
> gdb/regcache.c | 11 ++-
> gdb/remote.c | 20 +++--
> gdb/stack.c | 33 +++++++-
> gdb/testsuite/gdb.threads/killed-outside.exp | 11 ++-
> .../gdb.tui/multi-exit-remove-inferior.c | 21 +++++
> .../gdb.tui/multi-exit-remove-inferior.exp | 80 +++++++++++++++++++
> 7 files changed, 166 insertions(+), 13 deletions(-)
> create mode 100644 gdb/testsuite/gdb.tui/multi-exit-remove-inferior.c
> create mode 100644 gdb/testsuite/gdb.tui/multi-exit-remove-inferior.exp
>
> --
> 2.17.1
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-12-04 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 16:57 Tankut Baris Aktemur
2020-11-13 16:57 ` [PATCH 1/3] gdb/testsuite: update the expected output in gdb.threads/killed-outside.exp Tankut Baris Aktemur
2020-11-13 16:57 ` [PATCH 2/3] gdb/regcache: return REG_UNAVAILABLE if raw_update raises NOT_AVAILABLE_ERROR Tankut Baris Aktemur
2020-11-13 16:57 ` [PATCH 3/3] gdb: raise and handle NOT_AVAILABLE_ERROR when accessing frame PC Tankut Baris Aktemur
2020-11-27 16:08 ` [PATCH 0/3] Querying registers of already-exited processes Aktemur, Tankut Baris
2020-12-04 11:36 ` Aktemur, Tankut Baris [this message]
2020-12-21 8:04 ` Aktemur, Tankut Baris
2021-01-15 15:05 ` Aktemur, Tankut Baris
2021-02-01 16:48 ` Aktemur, Tankut Baris
2021-02-10 7:47 ` Aktemur, Tankut Baris
2021-03-16 18:19 ` Aktemur, Tankut Baris
2021-03-29 14:13 ` Aktemur, Tankut Baris
2021-04-12 12:46 ` Aktemur, Tankut Baris
2021-04-21 12:22 ` Aktemur, Tankut Baris
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=SN6PR11MB28935A8A852B57CBDB20A993C4F10@SN6PR11MB2893.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).