From owner-freebsd-ports@FreeBSD.ORG Sun Mar 23 17:32:22 2008 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8BE9106566B; Sun, 23 Mar 2008 17:32:22 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by mx1.freebsd.org (Postfix) with ESMTP id B494B8FC14; Sun, 23 Mar 2008 17:32:22 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=mMzCV2lhh6PDXc5VCPhiffKuh45zO05f0Z0dOV+ONFXlIr/c1GeqJzHLV6zgI1wX; h=Received:Subject:From:To:Cc:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [24.144.77.185] (helo=[192.168.2.10]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JdTka-0001aI-R9; Sun, 23 Mar 2008 13:12:53 -0400 From: Stephen Clark To: barner@FreeBSD.org Content-Type: text/plain Date: Sun, 23 Mar 2008 13:12:42 -0400 Message-Id: <1206292362.18333.3.camel@joker4.seclark.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-3.fc8) Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79145bd36cee1b65bde9ac2ff79ed0f386350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 24.144.77.185 Cc: ports@FreeBSD.org Subject: FreeBSD Port: valgrind-snapshot-352_7 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Mar 2008 17:32:23 -0000 Hello, I am trying to use valgrind on fbsd 6.2 patch 7 to find a memory leak in an ecpg postgresql app. When I run valgrind after a few minutes I get this error and valgrind terminates. Ideas? PORTNAME= valgrind PORTVERSION= 352 PORTREVISION= 7 CATEGORIES= devel valgrind: vg_malloc2.c:1008 (vgPlain_arena_malloc): Assertion `new_sb != ((void*)0)' failed. ==4166== at 0xB802BE1F: (within /usr/local/lib/valgrind/stage2) ==4166== by 0xB802BE1E: (within /usr/local/lib/valgrind/stage2) ==4166== by 0xB802BE5D: vgPlain_core_assert_fail (in /usr/local/lib/valgrind/stage2) ==4166== by 0xB8028091: vgPlain_arena_malloc (in /usr/local/lib/valgrind/stage2) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==4166== at 0x3C03894B: calloc (in /usr/local/lib/valgrind/vgpreload_memcheck.so) Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: valgrind.kde.org In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks.