public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Emil Velikov via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Glibc commit causing regression in gdb
Date: Fri, 16 Apr 2021 10:35:14 +0200	[thread overview]
Message-ID: <87y2dizkxp.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CACvgo503_+82SyOLdcZ6Z2_fh8H_A5GrM6G5fzDgUnP7xT6uHA@mail.gmail.com> (Emil Velikov via Libc-alpha's message of "Thu, 15 Apr 2021 20:59:51 +0100")

* Emil Velikov via Libc-alpha:

> We have recently received a regression report in Arch Linux, where gdb
> attach fails with some applications.
> In particular, the issue originates in glibc 2.33, while gdb used is
> 10.1 and is 100% reproducible (here) with steam and gimp.
>
> Note that explicitly rebuilding gdb explicitly against the glibc does not help.
>
> After some digging I found the offending glibc commit
> 1daccf403b1bd86370eb94edca794dc106d02039 ("nptl: Move stack list
> variables into _rtld_global"). With the said commit the
> td_ta_map_lwp2thr() call in GDB fails, resulting in the infamous
>
> Error while reading shared library symbols for /usr/lib/libpthread.so.0:
> Cannot find user-level thread for LWP 2999060: generic error

> Can anyone confirm if the issue is reproducible with other distros?

There's a separate thread about this on the gdb-patches list, under the
slightly misleading subject of “GDB 10.2 Release -- 2021-04-11 update”:

  <https://sourceware.org/pipermail/gdb-patches/2021-April/thread.html>

I believe there was an earlier discussion as well, but I can't find it
right now.

Thanks,
Florian


  reply	other threads:[~2021-04-16  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 19:59 Emil Velikov
2021-04-16  8:35 ` Florian Weimer [this message]
2021-04-16 10:54   ` Emil Velikov
2021-04-16 10:59     ` Florian Weimer

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=87y2dizkxp.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@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).