Date: Sat, 13 Jan 2001 17:47:53 +1030 From: Matthew Thyer <thyerm@camtech.net.au> To: Mike Heffner <mheffner@vt.edu> Cc: current@FreeBSD.org Subject: Re: Data corruption whilst debugging sonar module of ports/graph Message-ID: <3A600121.97AFD6EC@camtech.net.au> References: <XFMail.20010113010737.spock@techfour.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A600121.97AFD6EC>