From owner-freebsd-current@FreeBSD.ORG  Fri Jan  2 06:30:05 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 55F9516A4CE
	for <current@freebsd.org>; Fri,  2 Jan 2004 06:30:05 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D3C9A43D1D
	for <current@freebsd.org>; Fri,  2 Jan 2004 06:30:03 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i02ETujl026613;
	Fri, 2 Jan 2004 15:29:57 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: "Willem Jan Withagen" <wjw@withagen.nl>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 02 Jan 2004 13:15:42 +0100."
             <029c01c3d12a$2488c2c0$471b3dd4@dual> 
Date: Fri, 02 Jan 2004 15:29:56 +0100
Message-ID: <26612.1073053796@critter.freebsd.dk>
cc: questions@freebsd.iae.nl
cc: current@freebsd.org
Subject: Re: Strange calloc problem 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 14:30:05 -0000

In message <029c01c3d12a$2488c2c0$471b3dd4@dual>, "Willem Jan Withagen" writes:
>
>I'm running this compiler which is rather heap intensive and it crashed with
>a SigFault
>in calloc/malloc (I've tied both, but as expected calloc calls malloc)
>What suggestions are there further to track this down to the real problem.

Try running with malloc flags 'A' and 'J'

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.