Date: Tue, 31 Jan 2006 23:11:20 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Christian Brueffer <chris@unixpages.org> Cc: freebsd-current@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu> Subject: Re: panic: Memory modified after free Message-ID: <20060131220828.GA2953@garage.freebsd.pl> In-Reply-To: <20060131215021.GG4395@haakonia.hitnet.RWTH-Aachen.DE> References: <20060131212209.GA870@troutmask.apl.washington.edu> <20060131215021.GG4395@haakonia.hitnet.RWTH-Aachen.DE>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, Jan 31, 2006 at 10:50:21PM +0100, Christian Brueffer 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 +> > +> +> For the record, I got this as well today. Here it was on my notebook +> at system shutdown. Cool, so you have a chance to try memguard(9) and verify my patch to manual page:) --- memguard.9 30 Dec 2005 12:28:19 -0000 1.2 +++ memguard.9 31 Jan 2006 22:06:04 -0000 @@ -56,6 +56,9 @@ vm.memguard.desc=<memory_type> .Ed .Pp Where memory_type is a short description of memory type to monitor. +The short description of memory type is the second argument to +.Xr MALLOC_DECLARE 9 , +so one has to find it in the kernel source. .Pp To use memguard for memory type defined in a kernel module, one has to set .Va vm.memguard.desc -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD3+CHForvXbEpPzQRAmpnAKDSk0ALSIvFEbaJQCjtCTK78I6VMACg8wnY tOOF7vr97hhpFm1phuq6xHo= =LWO+ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060131220828.GA2953>