Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 31 Jan 2006 13:38:34 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: panic: Memory modified after free
Message-ID:  <20060131213834.GA1080@troutmask.apl.washington.edu>
In-Reply-To: <20060131213332.GA15250@xor.obsecurity.org>
References:  <20060131212209.GA870@troutmask.apl.washington.edu> <20060131213332.GA15250@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 31, 2006 at 04:33:32PM -0500, Kris Kennaway wrote:
> On Tue, Jan 31, 2006 at 01:22:09PM -0800, Steve Kargl wrote:
> > The system is a dual proc Tyan K8S Pro with 12 GB of memory.
> > The kernel is UP.  This was recorded by hand. I have the crash dump.
> > 
> > Memory modified after free 0xffffff02505e0c00(504) val=deadc0dd @
> > 0xffffff02505e0cd0
> > 
> > panic: Most recently used by DEVFS1
> 
> Set up memguard to watch this malloc type in order to obtain useful
> debugging.
> 

OK, I've read the memguard manpage and it says to add

vm.memguard.desc=<memory_type>

to /boot/loader.conf.  Where to I get info for what <memory_type>
actually means?

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060131213834.GA1080>