Date: Sat, 09 Nov 2002 17:45:33 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Aurelien Nephtali <aurelien.nephtali@wanadoo.fr> Cc: current@FreeBSD.ORG Subject: Re: Value 0xd0d0d0d0 ? Message-ID: <43160.1036860333@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 09 Nov 2002 13:49:30 %2B0100." <20021109124930.GA1429@nebula.wanadoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20021109124930.GA1429@nebula.wanadoo.fr>, Aurelien Nephtali writes: > >--lrZ03NoBR/3+SXJZ >Content-Type: text/plain; charset=iso-8859-15 >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >Hi, > >I would like to know where/when the value 0xd0d0d0d0 is assigned to a point= >er ? >Sometimes I have some pointers which have a correct value before and sudden= >ly >they got this odd 0xd0d0d0d0 value :/ When you have mistakes in your malloc(3)/free(3) handling. See the malloc(3) manual page. Try using electric-fence from the ports collection. -- 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. 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?43160.1036860333>