Re: panic: Memory modified after free
- From: Steve Kargl <sgk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 31 Jan 2006 13:38:34 -0800
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
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: panic: Memory modified after free
- From: Kris Kennaway
- Re: panic: Memory modified after free
- References:
- panic: Memory modified after free
- From: Steve Kargl
- Re: panic: Memory modified after free
- From: Kris Kennaway
- panic: Memory modified after free
- Prev by Date: Re: [RFC] what do we do with picobsd ?
- Next by Date: Re: panic: Memory modified after free
- Previous by thread: Re: panic: Memory modified after free
- Next by thread: Re: panic: Memory modified after free
- Index(es):