From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by sourceware.org (Postfix) with ESMTP id 6118B3857C7E for ; Fri, 16 Apr 2021 08:35:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6118B3857C7E Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-540-TXeAqCTXOGC3HXW5V5vJWg-1; Fri, 16 Apr 2021 04:34:58 -0400 X-MC-Unique: TXeAqCTXOGC3HXW5V5vJWg-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A039D1854E2B; Fri, 16 Apr 2021 08:34:57 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-113-139.ams2.redhat.com [10.36.113.139]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C65065D71F; Fri, 16 Apr 2021 08:34:56 +0000 (UTC) From: Florian Weimer To: Emil Velikov via Libc-alpha Subject: Re: Glibc commit causing regression in gdb References: Date: Fri, 16 Apr 2021 10:35:14 +0200 In-Reply-To: (Emil Velikov via Libc-alpha's message of "Thu, 15 Apr 2021 20:59:51 +0100") Message-ID: <87y2dizkxp.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2021 08:35:06 -0000 * 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 =E2=80=9CGDB 10.2 Release -- 2021-04-11 upda= te=E2=80=9D: I believe there was an earlier discussion as well, but I can't find it right now. Thanks, Florian