Re: panic: Memory modified after free

From: Kris Kennaway <kris_at_obsecurity.org>
Date: Fri, 24 Jun 2005 12:51:03 -0400
On Fri, Jun 24, 2005 at 05:37:55PM +0200, Thierry Herbelot wrote:
> Le Friday 24 June 2005 17:03, Kris Kennaway a ?crit :
> > On Fri, Jun 24, 2005 at 04:26:55PM +0200, Thierry Herbelot wrote:
> > > This is with an SMP machine (oldish BP6)
> >
> > Looks like you forgot to include the full panic...wasn't there a "last
> > used by FOO" also displayed?  If so, you should configure
> > DEBUG_MEMGUARD to watch this malloc type (some assembly required, but
> > it's pretty straightforward -- see Bosko Milekic's post to this
> > mailing list when he committed support describing how to do it) and
> > try to replicate the panic.
> 
> sorry if I forgot anything :
> this is the only message I had on the serial console :
> 
> [traditional dmesg startup messages]
> 
> Local package initialization:.
> Additional TCP options:.
> Starting background file system checks in 60 seconds.
> 
> Fri Jun 24 09:10:10 CEST 2005
> 
> FreeBSD/i386 (multi-cur.herbelot.nom) (ttyd0)
> 
> login: Jun 24 09:11:02 multi-cur su: thierry.herbelot to root on /dev/ttyp0
> panic: Memory modified after free 0xc15c1400(256) val=0 _at_ 0xc15c1400

Sorry, you're right..this is probably related to Mike's recent commit
that adds debugging and catches a new class of error.

Kris
Received on Fri Jun 24 2005 - 14:51:04 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:37 UTC