From owner-freebsd-current@FreeBSD.ORG Fri Jan 2 06:43:41 2004 Return-Path: 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 D124E16A4CE; Fri, 2 Jan 2004 06:43:41 -0800 (PST) Received: from freebee.digiware.nl (dsl144.iae.nl [212.61.62.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CD9643D48; Fri, 2 Jan 2004 06:43:40 -0800 (PST) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.9) with SMTP id i02Eir8A043085; Fri, 2 Jan 2004 15:44:53 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <02be01c3d13e$f4f01c60$471b3dd4@dual> From: "Willem Jan Withagen" To: "Poul-Henning Kamp" References: <26612.1073053796@critter.freebsd.dk> Date: Fri, 2 Jan 2004 15:44:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: questions@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2004 14:43:42 -0000 From: "Poul-Henning Kamp" > 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' That was one of my first attempts, but that did not help much. I hate Heap problems... 2 bytes changed, and now I'm no longer able to reproduce the error. So I've picked dmalloc from /usr/ports/devel to be my friend. And it shows that the compiler tools are seriously messing up the heap. --WjW