Date: Tue, 5 Mar 2019 17:26:52 +0100 From: Andrea Venturoli <ml@netfence.it> To: Kurt Jaeger <pi@opsec.eu> Cc: freebsd-ports@freebsd.org Subject: Re: devel/valgrind not working Message-ID: <143665c5-cbb3-57a3-081d-1a48568b8dd3@netfence.it> In-Reply-To: <20190305160643.GB47280@home.opsec.eu> References: <ea61170d-f5d5-ad7b-c488-7f067b387cbd@netfence.it> <20190305164343.109d3986@DaemONX> <e0a5fa31-1e44-3051-32e6-c20363bf2c60@netfence.it> <20190305160643.GB47280@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/5/19 5:06 PM, Kurt Jaeger wrote:
> Which begs the question: for which kernel was valgrind compiled ?
I had the original problem in a jail on machine "A"; valgrind was
compiled on an identical machine ("B") with Poudriere.
Machine "A" and "B" run the same kernel and userland (the latter
compiled for both on machine "B").
As a test, I also installed valgrind with portupgrade on machine "B"
(the one that runs Poudriere): the text I pasted comes from this setup
(so for sure same kernel, as valgrind was just freshly compiled).
I'll try rebuilding and reinstalling world (even if it should not really
change, apart from version number); if something different happens I'll
report back.
bye & Thanks
av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?143665c5-cbb3-57a3-081d-1a48568b8dd3>