Hi Denis,
Denis 'GNUtoo' Carikli skribis:
> * gnu/packages/valgrind.scm (valgrind/interactive)[native-inputs]:
> Add libc:debug
> [arguments]: Add patch-default-debuginfo-path phase
> [source]: Add patch.
> (valgrind-3.18)[source]: Add patch.
>
> * gnu/packages/commencement.scm (glibc-fi
On Thu, 07 Apr 2022 18:40:08 +0200
Ludovic Courtès wrote:
> Hi,
Hi,
> Unfortunately, until that branch is merge (most likely a few months
> from now), we’ll have to use the workaround you mentioned.
>
> Alternatively, maybe we could temporarily patch the ‘valgrind’ package
> such that it has ‘-
Hi,
Denis 'GNUtoo' Carikli skribis:
> The fact that Valgrind doesn't work out of the box seems to already be
> known[1] but I didn't find any bugreports on it.
Indeed. Fixed in 6b6fb78724869c03394d0e6dc2f50f0777f6d467 on
‘core-updates’ as discussed with Mark (mjw) a couple of days ago on IRC.
Hi,
The fact that Valgrind doesn't work out of the box seems to already be
known[1] but I didn't find any bugreports on it.
The workaround[1] mentioned is extremely useful but it's far from ideal.
For instance if you have a software that uses Valgrind in its tests
(for instance in 'make check')
