Re: gdb 10.1 with glibc 2.33 attach to process, td_ta_thr_iter fail

[Simon Marchi <simon.marchi@polymtl.ca>]

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