New comment by duncancmt on void-packages repository https://github.com/void-linux/void-packages/issues/25531#issuecomment-713101307 Comment: I'm re-opening this issue because #25605 did not fix the segfault here. Fortunately, it *did* fix `gdb`, so now I have a backtrace ``` # gdb --args `which mupdatedb` -f proc GNU gdb (GDB) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-linux-musl". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /bin/mupdatedb... Reading symbols from /usr/lib/debug//usr/bin/mupdatedb... (gdb) run Starting program: /usr/bin/mupdatedb -f proc Program received signal SIGSEGV, Segmentation fault. 0x0000fffff7fa4440 in strcmp (l=0xfffff7ffb5c0 "/boot", r=0xffffffffaaace020 ) at src/string/strcmp.c:5 5 src/string/strcmp.c: No such file or directory. (gdb) bt #0 0x0000fffff7fa4440 in strcmp (l=0xfffff7ffb5c0 "/boot", r=0xffffffffaaace020 ) at src/string/strcmp.c:5 #1 0x0000aaaaaaaaea94 in filesystem_is_excluded (path=0xfffff7ffb5c0 "/boot") at src/updatedb.c:404 #2 scan (path=0xfffff7ffb5c0 "/boot", cwd_fd=0xfffffffff178, relative=0xaaaaaaacc229 "boot", st_parent=) at src/updatedb.c:765 #3 0x0000aaaaaaaaf1d0 in scan_subdirs (st=0xfffffffff180, dir=) at src/updatedb.c:497 #4 scan (path=, cwd_fd=0xfffffffff328, relative=, st_parent=) at src/updatedb.c:825 #5 0x0000aaaaaaaac778 in main (argc=, argv=) at src/updatedb.c:1012 ```