Package: valgrind Severity: normal Hello,
Sourceware.org is having issues today so I can't research specifics, but Valgrind has supported the use of debuginfod's protocol to automatically get debug symbols just like how GDB does. Debian's (unofficial?) debuginfod instance is at debuginfod.debian.net and its use is documented elsewhere. Unlike GDB, Valgrind doesn't use libdebuginfod, but it invokes the command-line utility debuginfo-find from the debuginfod package. The Debian Valgrind package appears to have this functionality enabled by default, but Valgrind doesn't have any package relationship with debuginfod so users will only see this if they know what they're missing and dig in to finding why it's not working. Owing to that, I think adding a Recommends on debuginfod is the right way to go here. Suggests is too weak for something that the majority of users will want to have, as it allows getting symbols for Debian-packaged libraries even if a user's own custom application is what's currently under test, and debuginfod is cognizant of system-wide configuration and environment variables indicating users' preferences. This will save users a lot of frustration; I see an upload of Valgrind was just done, but can this be squeezed into Trixie? Thanks
signature.asc
Description: This is a digitally signed message part
