nptl_db 2.33 td_ta_thr_iter question

["Domen Stangar" <domen.stangar@gmail.com>]

Recently slackware updated libc from 2.22 to 2.23 and noticed that when 
attaching with gdb to working process, there are some notifications,
also there were some changes between 2.22 and 2.23 version in nptl_db.

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

I guess td_ta_thr_iter failed to return TD_OK, third time returned ok.
Anyone else noticed this ?

gdb is 10.1, used this commands to be more verbose gdb.
set debug libthread-db 1
maint set check-libthread-db 1

Might there be any test case for td_ta_thr_iter other than gdb ?

Thank you,
Domen