From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id EA1D93850407 for ; Mon, 22 Feb 2021 01:42:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EA1D93850407 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 11M1gRqH001704 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 21 Feb 2021 20:42:32 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 11M1gRqH001704 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 704A91EE39; Sun, 21 Feb 2021 20:42:27 -0500 (EST) Subject: Re: gdb 10.1 with glibc 2.33 attach to process, td_ta_thr_iter fail To: Domen Stangar , gdb@sourceware.org References: From: Simon Marchi Message-ID: Date: Sun, 21 Feb 2021 20:42:26 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Mon, 22 Feb 2021 01:42:27 +0000 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, 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: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2021 01:42:35 -0000 On 2021-02-20 11:33 a.m., Domen Stangar via Gdb wrote: > Hi, > is anyone running glibc 2.33 and tried to attach to process that is running threads. > Recently slackware did update from glibc 2.32 to glibc 2.33 and there are messages that weren't before. > So glibc 2.32 had no such issues. > I also used this commands in gdb. > set debug libthread-db 1 > maint set check-libthread-db 1 > So when attaching to process that has threads, i get this. > > Trying host libthread_db library: libthread_db.so.1. > Host libthread_db.so.1 resolved to: /lib64/libthread_db.so.1. > Running libthread_db integrity checks: > warning: libthread_db integrity checks failed: td_ta_thr_iter failed: generic error > Trying host libthread_db library: /lib64/libthread_db.so.1. > Running libthread_db integrity checks: > warning: libthread_db integrity checks failed: td_ta_thr_iter failed: generic error > thread_db_load_search returning 0 > warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. > Trying host libthread_db library: libthread_db.so.1. > Host libthread_db.so.1 resolved to: /lib64/libthread_db.so.1. > Running libthread_db integrity checks: > Got thread 0x7f2c184b5740 => 14613 => 0x7f2c184b5740 ... OK > Got thread 0x7f2c184b4640 => 14614 => 0x7f2c184b4640 ... OK > libthread_db integrity checks passed. > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > thread_db_load_search returning 1 > > Anyone else has this issues with glibc 2.33 ? > > Thank you, Domen > I see that on Arch Linux too, also glibc 2.33. I have not look into it yet. Simon