From owner-freebsd-ports@freebsd.org  Tue Mar  5 16:27:02 2019
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56CC7150727D
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Tue,  5 Mar 2019 16:27:02 +0000 (UTC) (envelope-from ml@netfence.it)
Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it
 [2.44.121.52])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "mailserver.netfence.it",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id B61E871FB0
 for <freebsd-ports@freebsd.org>; Tue,  5 Mar 2019 16:27:01 +0000 (UTC)
 (envelope-from ml@netfence.it)
Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18])
 (authenticated bits=0)
 by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id x25GQq04076130
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO);
 Tue, 5 Mar 2019 17:26:59 +0100 (CET) (envelope-from ml@netfence.it)
X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it
 [10.1.2.18] claimed to be alamar.ventu
Subject: Re: devel/valgrind not working
To: Kurt Jaeger <pi@opsec.eu>
Cc: freebsd-ports@freebsd.org
References: <ea61170d-f5d5-ad7b-c488-7f067b387cbd@netfence.it>
 <20190305164343.109d3986@DaemONX>
 <e0a5fa31-1e44-3051-32e6-c20363bf2c60@netfence.it>
 <20190305160643.GB47280@home.opsec.eu>
From: Andrea Venturoli <ml@netfence.it>
Message-ID: <143665c5-cbb3-57a3-081d-1a48568b8dd3@netfence.it>
Date: Tue, 5 Mar 2019 17:26:52 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101
 Thunderbird/60.5.2
MIME-Version: 1.0
In-Reply-To: <20190305160643.GB47280@home.opsec.eu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: B61E871FB0
X-Spamd-Bar: ------
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-6.98 / 15.00];
 NEURAL_HAM_MEDIUM(-1.00)[-1.000,0];
 NEURAL_HAM_SHORT(-0.98)[-0.984,0]; REPLY(-4.00)[];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2019 16:27:02 -0000

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.