Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76598 - Add glibc debuginfo
Attached to Project:
Arch Linux
Opened by Mark (markg85) - Wednesday, 16 November 2022, 11:25 GMT
Last edited by Morten Linderud (Foxboron) - Wednesday, 16 November 2022, 11:44 GMT
Opened by Mark (markg85) - Wednesday, 16 November 2022, 11:25 GMT
Last edited by Morten Linderud (Foxboron) - Wednesday, 16 November 2022, 11:44 GMT
|
DetailsValgrind gives me this error:
valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind: On Debian, Ubuntu: libc6-dbg valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. Could arch do 1 of the following: 1. Provide a package with debug symbols for glibc 2. Don't strip the symbols Either option would help devs out massively! And as arch is very often used by devs, it makes very much sense to go for either of those options. |
This task depends upon
Closed by Morten Linderud (Foxboron)
Wednesday, 16 November 2022, 11:44 GMT
Reason for closing: Not a bug
Wednesday, 16 November 2022, 11:44 GMT
Reason for closing: Not a bug
https://archlinux.org/news/debug-packages-and-debuginfod/