Hello, I am looking to have glibc debug symbols to use with perf and valgrind. To accomplish this I included system-debug and world-debug repos in my pacman.conf file, but no mirror of the default mirror list seems to have the package glibc-debug (404 error). I'm ok with downgrading glibc from 2.39-1 to an earlier version, if I can obtain the corresponding debug symbols (glibc-debug package).
TLDR: Can someone pls provide a resource for downloading (a somewhat current) glibc-debug package.
Same problem MrProblem
To be more precise, added these to pacman.conf
[system-debug]
Server = https://debuginfod.artixlinux.org/$repo/os/$arch
[world-debug]
Server = https://debuginfod.artixlinux.org/$repo/os/$arch
[lib32-debug]
Server = https://debuginfod.artixlinux.org/$repo/os/$arch
after -Syu I get
# pacman -S glibc-debug
...
error: failed retrieving file 'glibc-debug-2.37-3-x86_64.pkg.tar.zst' from debuginfod.artixlinux.org : The requested URL returned error: 503
warning: failed to retrieve some files
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
https://debuginfod.artixlinux.org/packages does not list glibc-debug as a package, something's wrong
Download the build files from gitea , build it yourself, and you'll have a debug package.
I'd suggest you Install the other packages as well though as Cflags may introduce differences from the repo version?
Thanks for the idea, but gitea doesn't seem to have the package either:/
https://gitea.artixlinux.org/explore/repos?q=glibc-debug
https://gitea.artixlinux.org/packages/glibc
glibc-debug is part of the glibc pkgbase
Edit:
Depending on your machine it takes a while to compile.
It's not uncommon for some of its tests to fail.
Should you encounter this and they are related to resolving / nss increasing the timeout for the tests can solve the issue.
Add --with-timeoutfactor=100 (Arbitrary number, smaller may suffice, you may even need larger?)
to the end of the local _configure_flags stanza.
You don't need to compile it all again. Run makepkg with the -e switch and makepkg will use the existing generated object files.
Or live on the edge and just comment out the check() section of the PKGBUILD.
Thanks a lot, compiling took more than an hour on my roughly 10 year old machine, but it in the end it did the job.
Do we need to manually compile glibc to get valgrind working? What's the point using debuginfod?