From: Simon Marchi <simon.marchi@polymtl.ca>
To: Domen Stangar <domen.stangar@gmail.com>, gdb@sourceware.org
Subject: Re: gdb 10.1 with glibc 2.33 attach to process, td_ta_thr_iter fail
Date: Fri, 5 Mar 2021 12:00:10 -0500 [thread overview]
Message-ID: <77fd7749-4caa-eac6-d14c-6632669319c4@polymtl.ca> (raw)
In-Reply-To: <b50d6e9b-9737-35dc-b4a9-49598ee9916f@polymtl.ca>
On 2021-02-21 8:42 p.m., Simon Marchi via Gdb wrote:
>
>
> 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
>
FYI I opened this bug about this:
https://sourceware.org/bugzilla/show_bug.cgi?id=27526
Simon
prev parent reply other threads:[~2021-03-05 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 16:33 Domen Stangar
2021-02-22 1:42 ` Simon Marchi
2021-03-05 17:00 ` Simon Marchi [this message]
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=77fd7749-4caa-eac6-d14c-6632669319c4@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=domen.stangar@gmail.com \
--cc=gdb@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).