From: Pedro Alves <pedro@palves.net>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] glibc-2.34: Fix internal error when running gdb.base/gdb-sigterm.exp
Date: Sat, 10 Jul 2021 20:07:28 +0100 [thread overview]
Message-ID: <a3253850-5284-f0d4-ff29-c72d6fff4eda@palves.net> (raw)
In-Reply-To: <20210710025129.201884-3-kevinb@redhat.com>
Hi Kevin!
On 2021-07-10 3:51 a.m., Kevin Buettner via Gdb-patches wrote:
> The reason that the problem occurs with glibc-2.34 is that
> libthread_db will always be loaded now; thus the wait() machinery
> found in linux-thread-db.c is used instead of linux_nat_target::wait
> (which is found in linux-nat.c).
>
> gdb/ChangeLog:
>
> * thread.c (any_thread_of_inferior): Don't call inferior_thread()
> when there is no current thread.
This isn't right. The real bug is that inferior_ptid and current_thread_ got
out of sync. Where did that happen? What set inferior_ptid without using
switch_to_thread & friends?
next prev parent reply other threads:[~2021-07-10 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 2:51 [PATCH 0/2] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error Kevin Buettner
2021-07-10 2:51 ` [PATCH 1/2] Handle recursive internal problem in gdb_internal_error_resync Kevin Buettner
2021-07-10 2:51 ` [PATCH 2/2] glibc-2.34: Fix internal error when running gdb.base/gdb-sigterm.exp Kevin Buettner
2021-07-10 19:07 ` Pedro Alves [this message]
2021-07-13 23:35 ` Kevin Buettner
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=a3253850-5284-f0d4-ff29-c72d6fff4eda@palves.net \
--to=pedro@palves.net \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).