Hi Chris,
It's a bit moot as the bug is already solved
On 13-04-2025 23:06, Chris Hofstaedtler wrote:
> I think you are implying a finer detail that is lost on me.
Let me try again. The other bug is about valgrind Recommends a package
that doesn't exist. That's clearly RC, it can be fixed
Hi Paul,
* Paul Gevers [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, thi
Hi zeha,
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
On Sun, 13 Apr 2025 at 11:23, Chris Hofstaedtler 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 wrote:
> > > For the usual case where debug symbols are only used
> > > when debugging in a debugger this is no problem,
> >
On Thu, Apr 10, 2025 at 07:21:03PM +0200, Paul Gevers wrote:
> On Wed, 06 Dec 2023 02:05:07 +0200 Adrian Bunk 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
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
Dear maintainer,
On Wed, 06 Dec 2023 02:05:07 +0200 Adrian Bunk 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.debia
Hi,
On 2/11/25 12:41, Vincent Lefevre wrote:
I'm also wondering about the current status of this bug. After
more than one year, there haven't been any comments.
Sorry for not being of great help on this, but just for information, it
has been also one year since
I'm holding it's upgrade:
##
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
>
> -dbgsym packages are not part of the normal archive,
> and they can therefore not be expected to be pulled in
> by normal dependencies.
>
> For th
Package: valgrind
Version: 1:3.20.0-1
Severity: serious
X-Debbugs-Cc: Adam Borowski
-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 debugge
10 matches
Mail list logo
