Date: Fri, 19 Sep 1997 07:40:55 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "Andrew Atrens" <atrens@nortel.ca> Cc: hackers@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Message-ID: <12157.874647655@critter.freebsd.dk> In-Reply-To: Your message of "18 Sep 1997 17:59:00 EDT." <199709182204.AAA11611@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199709182204.AAA11611@critter.freebsd.dk>, "Andrew Atrens" writes: >In message "Bug in malloc/free (was: Memory leak in getservbyXXX?)", phk@critt >er.freebsd.dk writes: >> > >> This is about the only way you could get it to loop I think. That means >> that somebody wrote to memory malloc hadn't passed them (ie: your code). >> >> This would indicate a bug of the class where memory is written to after >> being free()'ed, a kind of bug which phkmalloc makes no attempt to catch. > >Why not have free() shred memory its releasing? Shredding memory with high >values can often cause the offending code (which is still attempting >to r/w this memory) to bus error. options 'J' does that. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12157.874647655>