Ahh, I came across this article trying and failing to rebuild glibc in debug mode on Arch Linux, and it would always error out due to _FORTIFY_SOURCE (eeg. http

Ahh, I came across this article trying and failing to rebuild glibc in debug mode on Arch Linux, and it would always error out due to _FORTIFY_SOURCE (eeg. https://bbs.archlinux.org/viewtopic.php?id=245755 https://bbs.archlinux.org/viewtopic.php?id=245755). IIRC I tried creating a chroot but ran into the same error (or couldn't make the chroot work, forgot which). In the end I gave up rebuilding glibc in debug mode (since it would've slowed down all my programs). I still don't know what I did wrong; maybe glibc is just incompatible with optimizations off. Nowadays Arch uploads package symbols to debug packages and servers accessible by debuginfod (https://wiki.archlinux.org/title/Debugging/Getting_traces https://wiki.archlinux.org/title/Debugging/Getting_traces), but I've observed debuginfod greatly slows down gdb and valgrind and strace (so I don't set the DEBUGINFOD_URLS environment variable by default, only when actually debugging).