From owner-freebsd-current Sat Jan 13 14:25: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id EDF9D37B402 for ; Sat, 13 Jan 2001 14:24:43 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0DMNk159924; Sat, 13 Jan 2001 14:23:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A600121.97AFD6EC@camtech.net.au> Date: Sat, 13 Jan 2001 14:24:46 -0800 (PST) From: John Baldwin To: Matthew Thyer Subject: Re: Data corruption whilst debugging sonar module of ports/graph Cc: current@FreeBSD.org, Mike Heffner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-01 Matthew Thyer wrote: > 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. 0xdeadc0de is used by kernel malloc, and 0xd0d0d0d0 by the userland malloc, AFAIK. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message