From owner-freebsd-questions@FreeBSD.ORG Wed Nov 21 20:28:15 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E3385FC9 for ; Wed, 21 Nov 2012 20:28:15 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id C24F18FC08 for ; Wed, 21 Nov 2012 20:28:15 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TbGu1-0001rt-JX for freebsd-questions@freebsd.org; Wed, 21 Nov 2012 12:28:09 -0800 Date: Wed, 21 Nov 2012 12:28:09 -0800 (PST) From: Jakub Lach To: freebsd-questions@freebsd.org Message-ID: <1353529689596-5762993.post@n5.nabble.com> Subject: valgrind on pure amd64 (64 bit system _only_) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 20:28:15 -0000 What's state of valgrind port on pure amd64 system? Here, it core dumps upon linking both with clang and gcc47, with complaint that looks suspicious (expected i386 not X86_64 or something to that effect). -- View this message in context: http://freebsd.1045724.n5.nabble.com/valgrind-on-pure-amd64-64-bit-system-only-tp5762993.html Sent from the freebsd-questions mailing list archive at Nabble.com.