Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1241751 > unrolled thread

Bug#1057621: valgrind should not drop valgrind-dbg

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1057621: valgrind should not drop valgrind-dbg Chris Hofstaedtler <zeha@debian.org> - 2025-04-13 11:30 +0200
    Bug#1057621: valgrind should not drop valgrind-dbg Chris Hofstaedtler <zeha@debian.org> - 2025-04-13 23:10 +0200

#1241751 — Bug#1057621: valgrind should not drop valgrind-dbg

[Multipart message — attachments visible in raw view] — view raw

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.

Possible debdiff attached.

Chris

[toc] | [next] | [standalone]

#1241886

Hi Paul,

* Paul Gevers <elbrus@debian.org> [250413 20:25]:
>On 13-04-2025 11:23, Chris Hofstaedtler wrote:
>>>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: ...)
>
>
>But that's the other RC bug against valgrind. I was explicitly 
>interested if the lack of *a* debug symbols package in Recommends is 
>to be considered RC in itself.

I think you are implying a finer detail that is lost on me.

valgrind was recommending a package that is not available in main. 
I'm not sure what the status would be, if valgrind had recommended 
valgrind-dbgsym instead. That would also be not installable on a 
system configured with the default APT sources setup.

The second bug seems to describe the exactly same problem.

Chris

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web