From owner-freebsd-stable@FreeBSD.ORG  Sat Dec 28 02:31:06 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 577D53C4
 for <freebsd-stable@freebsd.org>; Sat, 28 Dec 2013 02:31:06 +0000 (UTC)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com
 [IPv6:2607:f8b0:400c:c03::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 16C041514
 for <freebsd-stable@freebsd.org>; Sat, 28 Dec 2013 02:31:06 +0000 (UTC)
Received: by mail-vc0-f182.google.com with SMTP id lc6so5132058vcb.13
 for <freebsd-stable@freebsd.org>; Fri, 27 Dec 2013 18:31:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=4z9DiFeM2UYv5vSIpRPKGQxy9ml4tDZZV9Gzy6FqYlU=;
 b=VkID0HLvMjAF/cAwUuUpaclq+GpSMZGtLVHOaURN3db6p2qxV8VxNOZ9FuV/q3MnjG
 BcVi9SR/0m/nFLLKzL0BRA5DV7P0IUGkFTHG/J9XamdR+C1WU/3e98NKlpOdBB4/JDJR
 KcRpw8ku1zux2IvFXlT6Gcm6OHIQrziN1twCoMBbXX+6VYAX/m/8LahIniOysSnE4tNS
 jfLpJ51F29abWoyzDM9jkyNNCoY+X7Ik8EyUzfO6NS9AsVcrR2YRxzH44Q3/6/T3MbUK
 aBAfuI5bxHS/dg9mbgdJ1XPMa3gZ3nTz2IZ744Ta5rcmdO+q3sPb7McZKwncWHfm9Cez
 Nmnw==
MIME-Version: 1.0
X-Received: by 10.220.182.137 with SMTP id cc9mr181359vcb.62.1388197865033;
 Fri, 27 Dec 2013 18:31:05 -0800 (PST)
Received: by 10.58.37.135 with HTTP; Fri, 27 Dec 2013 18:31:04 -0800 (PST)
Date: Fri, 27 Dec 2013 21:31:04 -0500
Message-ID: <CADt0fhwd4AtuHq0DPFHyiHUJumOxe8Tog53B5BU1uSDLZWvWWg@mail.gmail.com>
Subject: Valgrind Broken on 10.0?
From: Shawn Webb <lattera@gmail.com>
To: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.17
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Dec 2013 02:31:06 -0000

Hey All,

So overall, I'm loving 10.0 (running on the STABLE branch). Really great
job. However, it seems that Valgrind is confused about where objects loaded
in memory are located. Please forgive my forgetfulness, but I seem to
recall a discussion (either on current@ or stable@) regarding changes to
the virtual memory management system and how those changes could affect
userland applications like Valgrind. Can someone point me in the right
direction if that's the case? Otherwise, what are some courses of action I
could take to get symbols to resolve in Valgrind? 9-stable doesn't have
this problem. 11-current exhibits the same behavior as 10-stable.

Below you'll find a link to the log of Valgrind failing on a specific
clamav unit test. I'm running 10-stable in bhyve under an 11-current system.

Failed unit test log: http://ix.io/9xQ (if you'd prefer me paste the log
(quite lengthy) in an email, let me know).

Thanks,

Shawn Webb