From owner-freebsd-current  Fri Jan 12 23:16: 5 2001
Delivered-To: freebsd-current@freebsd.org
Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84])
	by hub.freebsd.org (Postfix) with ESMTP id F275F37B400
	for <current@FreeBSD.org>; Fri, 12 Jan 2001 23:15:46 -0800 (PST)
Received: from camtech.net.au ([203.55.245.112])
          by mta04.mail.mel.aone.net.au with ESMTP
          id <20010113071537.DAMG19873.mta04.mail.mel.aone.net.au@camtech.net.au>;
          Sat, 13 Jan 2001 18:15:37 +1100
Message-ID: <3A600121.97AFD6EC@camtech.net.au>
Date: Sat, 13 Jan 2001 17:47:53 +1030
From: Matthew Thyer <thyerm@camtech.net.au>
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mike Heffner <mheffner@vt.edu>
Cc: current@FreeBSD.org
Subject: Re: Data corruption whilst debugging sonar module of ports/graph
References: <XFMail.20010113010737.spock@techfour.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Heffner wrote:
> 
> On 13-Jan-2001 Matthew Thyer wrote:
> 
> | Does anyone recognise where 0xd0d0d0d0 may have come from ?
> |
> 
> [snip]
> 
> Read the "Tuning" section of malloc(3). 0xd0 is what allocated and deallocated
> memory is set to. xscreensaver is probably not initializing malloc()'d memory,
> and therefore it's left at 0xd0. A work around is to turn off this feature:
> 
> ln -s aj /etc/malloc.conf
> 
> however, xscreensaver should be fixed instead.

Yes, that's what I'm trying to achieve.  I thought it was "0xdeadcode"
that got put in the malloc'd memory but if that's changed then thanks
for the lead.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message