From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 23 20:03:40 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E878E16A4CE for ; Mon, 23 Aug 2004 20:03:40 +0000 (GMT) Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0813143D41 for ; Mon, 23 Aug 2004 20:03:40 +0000 (GMT) (envelope-from barner@in.tum.de) Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id B831FC1B6; Mon, 23 Aug 2004 22:03:39 +0200 (CEST) Date: Mon, 23 Aug 2004 22:03:39 +0200 From: Simon Barner To: Miguel Mendez Message-ID: <20040823200339.GA5717@zi025.glhnet.mhn.de> References: <20040823210324.567ea3a3.flynn@energyhq.es.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <20040823210324.567ea3a3.flynn@energyhq.es.eu.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new/sophie/sophos at mailrelay1.informatik.tu-muenchen.de cc: freebsd-hackers@freebsd.org Subject: Re: valgrind on 5.3BETA1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Aug 2004 20:03:41 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Miguel Mendez wrote: > Hi all, >=20 > Is anybody using valgrind on 5.3BETA1 or newer? I've been using it for a > while on 5.2.1 without any problems, until I upgraded my system to > RELENG_5. The program works but it never exits after running your > program, it gets stuck into `umtx' state indefinitely. This is happening > with both plain jane valgrind and valgrind-snapshot ports. Is this > already a known issue?=20 Hi, there is a closed problem report in the database: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D68992 At the end of that PR, there is a patch that seems to work around the problem. Could you please test it? Simon --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBKk2bCkn+/eutqCoRAsi5AKCi3XVsvRSPvTWvpylS3IvgotVUkACg4f10 /OdB2PQdG2C6VohlbycXn5A= =ov5x -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0--