On Sun, 13 Apr 2025 at 11:23, Chris Hofstaedtler <z...@debian.org> wrote: > > On Thu, Apr 10, 2025 at 07:21:03PM +0200, Paul Gevers wrote: > > On Wed, 06 Dec 2023 02:05:07 +0200 Adrian Bunk <b...@debian.org> wrote: > > > For the usual case where debug symbols are only used > > > when debugging in a debugger this is no problem, > > > but valgrind-dbg is (like libc6-dbg) an exception: > > > > > > Package: valgrind > > > Recommends: valgrind-dbg, gdb > > > > > > https://sources.debian.org/src/valgrind/1%3A3.20.0-2/debian/README.Debian/#L11-L16 > > > > > > Debian's valgrind package comes stripped of any debug symbols, which are > > > provided by the valgrind-dbg package. Note that it's recommended to > > > install > > > such package because without those symbols valgrind may generate less > > > helpful error messages in certain situations, or not work at all. > > > > Do you agree with the submitter of this bug that the lack of debug symbols > > available via Recommends is a release critical bug? I'm not an experienced > > valgrind user, but with my Release Team member hat on, this looks a bit > > exaggerated. > (I believe the RC policy includes unavailable packages in > Recommends: ...) > > > Hope to hear your opinion. > > > > Without an exception for the freeze policy, fixing this bug by reintroducing > > the valgrind-dbg package is going to be extremely tight, given that it has > > to pass NEW and that the window for new binary packages closes on > > 2025-04-15. > > If the debug symbols are as relevant as the README claims, the > obvious solution is to include them in the main package.
Thank you for your suggestion. We can even reduce the scope a little more: We only need to include the debug symbols for the vgpreload* files, as upstream explains: https://valgrind.org/docs/manual/dist.readme-packagers.html I am uploading a fix (valgrind 1:3.24.0-3) to unstable as we speak. With that said, I agree that the severity of this issue is a little exaggerated. Valgrind is a framework that provides multiple analysis tools. Only the memcheck tool (granted, perhaps the most well-known tool) is affected by the lack of debug symbols in vgpreload*. Other tools, like callgrind or cachegrind, fully work as-is. -- Best regards, Michael
