1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1057621: valgrind should not drop valgrind-dbg

    From Vincent Lefevre@21:1/5 to Adrian Bunk on Tue Feb 11 12:50:01 2025
    Hi,

    On 2023-12-06 02:05:07 +0200, Adrian Bunk wrote:
    Package: valgrind
    Version: 1:3.20.0-1
    Severity: serious
    X-Debbugs-Cc: Adam Borowski <kilobyte@angband.pl>

    -dbgsym packages are not part of the normal archive,
    and they can therefore not be expected to be pulled in
    by normal dependencies.

    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:

    Related to this bug, I've reported

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095737

    about the unsatisfiable recommends on valgrind-dbg.

    Providing valgrind-dbg again (so fixing this bug 1057621) would
    be a way to fix bug 1095737.

    I'm also wondering about the current status of this bug. After
    more than one year, there haven't been any comments.

    --
    Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
    100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
    Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Ch. Eigler@21:1/5 to All on Thu Apr 10 21:30:01 2025
    Hi -

    Please beware a possible naming confusion: "valgrind-gdb" vs
    "valgrind-dbg". The former is a relatively recently added subpackage
    for gdb interfacing support, and has nothing to do with valgrind's
    own debuginfo.

    - FChE

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael Stapelberg@21:1/5 to Chris Hofstaedtler on Sun Apr 13 12:10:01 2025
    On Sun, 13 Apr 2025 at 11:23, Chris Hofstaedtler <zeha@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 <bunk@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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Gevers@21:1/5 to Chris Hofstaedtler on Sun Apr 13 20:30:02 2025
    To: 1057621@bugs.debian.org
    To: bunk@debian.org (Adrian Bunk)
    Copy: ghedo@debian.org (Alessandro Ghedini)
    Copy: stapelberg@debian.org (Michael Stapelberg)

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------VhXwTNPSzJ0J3SL2L7O0gFih
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGkgemVoYSwNCg0KT24gMTMtMDQtMjAyNSAxMToyMywgQ2hyaXMgSG9mc3RhZWR0bGVyIHdy b3RlOg0KPj4gRG8geW91IGFncmVlIHdpdGggdGhlIHN1Ym1pdHRlciBvZiB0aGlzIGJ1ZyB0 aGF0IHRoZSBsYWNrIG9mIGRlYnVnIHN5bWJvbHMNCj4+IGF2YWlsYWJsZSB2aWEgUmVjb21t ZW5kcyBpcyBhIHJlbGVhc2UgY3JpdGljYWwgYnVnPyBJJ20gbm90IGFuIGV4cGVyaWVuY2Vk DQo+PiB2YWxncmluZCB1c2VyLCBidXQgd2l0aCBteSBSZWxlYXNlIFRlYW0gbWVtYmVyIGhh dCBvbiwgdGhpcyBsb29rcyBhIGJpdA0KPj4gZXhhZ2dlcmF0ZWQuDQoNCj4gKEkgYmVsaWV2 ZSB0aGUgUkMgcG9saWN5IGluY2x1ZGVzIHVuYXZhaWxhYmxlIHBhY2thZ2VzIGluDQo+IFJl Y29tbWVuZHM6IC4uLikNCg0KDQpCdXQgdGhhdCdzIHRoZSBvdGhlciBSQyBidWcgYWdhaW5z dCB2YWxncmluZC4gSSB3YXMgZXhwbGljaXRseSANCmludGVyZXN0ZWQgaWYgdGhlIGxhY2sg b2YgKmEqIGRlYnVnIHN5bWJvbHMgcGFja2FnZSBpbiBSZWNvbW1lbmRzIGlzIHRvIA0KYmUg Y29uc2lkZXJlZCBSQyBpbiBpdHNlbGYuDQoNClBhdWwNCg0K

    --------------VhXwTNPSzJ0J3SL2L7O0gFih--

    -----BEGIN PGP SIGNATURE-----

    wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmf8AY8FAwAAAAAACgkQnFyZ6wW9dQrK HggAj2/Tka0BIEeN+OJ/1eQeJzJNPmLNc0F6FjHPVWFokWb6qohWarHQAOtq8b9rCUarqvsnWNTT Y4sra3MU/NIO8UfoLXhlzVVwvMxO/wcGoscJlJB477JqpRqXDGpUBcS2MbfncVzemIdw6M/3gAKw jAp6/Fy4AlQxP4Kxca2BEH5cTyKYqvRcvJpkQqJgOJD0NKeNoYRaV1vaISHMTLEk5CJw+QvBT42U oSlj92Dxm1NXXvw5HYY2jfhC1xNCX5DHCz1cmtj6gYtNc433D4dCi5hL7GI3huwLhPAwwfT+MB2e xIEFkulnfJX9kioL8cJjPRFF+gE5pokE4fTLoNFE5A==
    =lU4e
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)