Hi Julian!
On 2024-01-12 01:47, Julian Andres Klode wrote:
> Either way, these are harmless
I'm not saying they're harmful, what I'm saying is:
1) the errors you see on armhf when building apt without
stack-clash-protection are the same valgrind reports on amd64 as
well. Hence, you could c
On Thu, Jan 11, 2024 at 10:18:58PM +0100, Emanuele Rocca wrote:
> Hi Julian,
>
> On 2024-01-11 05:46, Julian Andres Klode wrote:
> > And there aren't any hard errors. We could zero initialize
> > those or add supressions to make things look nicer I suppose.
>
> Mmmh no, they are all actual errors
Hi Julian,
On 2024-01-11 05:46, Julian Andres Klode wrote:
> And there aren't any hard errors. We could zero initialize
> those or add supressions to make things look nicer I suppose.
Mmmh no, they are all actual errors as far as valgrind is concerned.
The thing is, you're running valgrind witho
On Thu, Jan 11, 2024 at 03:53:17PM +0100, Emanuele Rocca wrote:
> Hi Julian,
>
> On 2024-01-08 10:28, Julian Andres Klode wrote:
> > (in Ubuntu we have partially recovered by disabling stack clash
> > protection but it crashes on invalid writes there, I suppose we need
> > to rebuild some more apt
Hi Julian,
On 2024-01-08 10:28, Julian Andres Klode wrote:
> (in Ubuntu we have partially recovered by disabling stack clash
> protection but it crashes on invalid writes there, I suppose we need
> to rebuild some more apt dependencies without the flag...).
The 'invalid writes' issue seems unrela
Control: retitle -1 valgrind: Access not within mapped region on armhf
Hello Paul and Julian,
On 2023-12-24 07:31, Paul Gevers wrote:
> On 23-12-2023 20:40, Julian Andres Klode wrote:
> > the logs for well known bugs so that you don't end up filing bugs
> > against every package broken by valgrin
Control: clone -1 -2
Control: reassign -2 valgrind
Control: retitle -2 valgrind: armhf is broken
On Sat, Dec 23, 2023 at 08:46:27AM +0100, Paul Gevers wrote:
> Source: apt
> Version: 2.7.6
> Severity: serious
> Control: close -1 2.7.7
> Tags: sid trixie
> User: release.debian@packages.debian.o
Hi Julian,
On 23-12-2023 20:40, Julian Andres Klode wrote:
I know this is automated but I feel lije it would be sensible to scan
It's *mostly* automated.
the logs for well known bugs so that you don't end up filing bugs
against every package broken by valgrind's missing support for the new
N
On Sat, Dec 23, 2023 at 08:46:27AM +0100, Paul Gevers wrote:
> Source: apt
> Version: 2.7.6
> Severity: serious
> Control: close -1 2.7.7
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
> Dear maintainer(s),
>
> The Release Team considers packages that
Source: apt
Version: 2.7.6
Severity: serious
Control: close -1 2.7.7
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Re
10 matches
Mail list logo
