From: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error
Date: Fri, 9 Jul 2021 22:51:27 -0400 [thread overview]
Message-ID: <20210710025129.201884-1-kevinb@redhat.com> (raw)
These patches fix problems that I encountered while running
gdb.base/gdb-sigterm.exp on machines with a pre-release of glibc-2.34
installed.
Kevin Buettner (2):
Handle recursive internal problem in gdb_internal_error_resync
glibc-2.34: Fix internal error when running gdb.base/gdb-sigterm.exp
gdb/testsuite/lib/gdb.exp | 4 ++++
gdb/thread.c | 3 ++-
2 files changed, 6 insertions(+), 1 deletion(-)
--
2.32.0
next reply other threads:[~2021-07-10 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 2:51 Kevin Buettner via Gdb-patches [this message]
2021-07-10 2:51 ` [PATCH 1/2] Handle recursive internal problem in gdb_internal_error_resync Kevin Buettner via Gdb-patches
2021-07-10 2:51 ` [PATCH 2/2] glibc-2.34: Fix internal error when running gdb.base/gdb-sigterm.exp Kevin Buettner via Gdb-patches
2021-07-10 19:07 ` Pedro Alves
2021-07-13 23:35 ` Kevin Buettner via Gdb-patches
2021-07-14 0:07 ` 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=20210710025129.201884-1-kevinb@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=kevinb@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