This is with procps-ng-3.3.15-5.fc30.x86_64, glibc-2.29-12.fc30.x86_64 and libasan-9.1.1-1.fc30.x86_64. Trying to run $ LD_PRELOAD=/usr/lib64/libasan.so.5 pkill --help deadlocks with this backtrace: Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f4024b045f8 in pthread_rwlock_wrlock () from /lib64/libpthread.so.0 Thread 1 (Thread 0x7f402455c840 (LWP 26884)): #0 0x00007f4024b045f8 in pthread_rwlock_wrlock () from /lib64/libpthread.so.0 #1 0x00007f4024b5c833 in textdomain () from /lib64/libc.so.6 #2 0x00007f4024db2531 in __interceptor_textdomain (domainname=0x564aca39f176 "procps-ng") at ../../../../libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:401 #3 0x0000564aca39c7b5 in main (argc=2, argv=0x7ffe7382c458) at pgrep.c:913 Similarly for example with $ LD_PRELOAD=/usr/lib64/libasan.so.5 ps --help with this backtrace (with installed debuginfo also for glibc this time): Using host libthread_db library "/lib64/libthread_db.so.1". futex_abstimed_wait (private=0, abstime=0x0, expected=2, futex_word=0x7f6df1874be8 <_nl_state_lock+8>) at ../sysdeps/unix/sysv/linux/futex-internal.h:172 172 int err = lll_futex_timed_wait_bitset (futex_word, expected, abstime, Thread 1 (Thread 0x7f6df10ed840 (LWP 26912)): #0 futex_abstimed_wait (private=0, abstime=0x0, expected=2, futex_word=0x7f6df1874be8 <_nl_state_lock+8>) at ../sysdeps/unix/sysv/linux/futex-internal.h:172 #1 __pthread_rwlock_wrlock_full (abstime=0x0, rwlock=0x7f6df1874be0 <_nl_state_lock>) at pthread_rwlock_common.c:807 #2 __GI___pthread_rwlock_wrlock (rwlock=0x7f6df1874be0 <_nl_state_lock>) at pthread_rwlock_wrlock.c:27 #3 0x00007f6df16e7833 in __textdomain (domainname=0x559a79ebb1a8 "procps-ng") at textdomain.c:73 #4 0x00007f6df1943531 in __interceptor_textdomain (domainname=0x559a79ebb1a8 "procps-ng") at ../../../../libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:401 #5 0x0000559a79eafc6f in main (argc=2, argv=0x7ffcd36cffd8) at ps/display.c:628
I get a very similar deadlock with gedit, epiphany,... . I do not know how to reproduce this out of those applications, even I tried. This is with rawhide, glibc-2.30.9000-4.fc32.x86_64, but I see a similar deadlock with glibc-2.29-15.fc30.x86_64. It's very hard to debug anything with libasan when it deadlocks right after start.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.