panic: Memory modified after free
Pawel Jakub Dawidek
pjd at FreeBSD.org
Tue Jan 31 14:11:40 PST 2006
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
--- 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>
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.
To use memguard for memory type defined in a kernel module, one has to
Pawel Jakub Dawidek http://www.wheel.pl
pjd at FreeBSD.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20060131/8258602e/attachment.bin
More information about the freebsd-current