On Tue, Jan 31, 2006 at 05:47:21PM -0500, Kris Kennaway wrote: +> On Tue, Jan 31, 2006 at 11:11:20PM +0100, Pawel Jakub Dawidek wrote: +> > 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 _at_ +> > +> > 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 +> > _at__at_ -56,6 +56,9 _at__at_ 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. +> +> ITYM MALLOC_DEFINE? Yes, DEFINE. -- Pawel Jakub Dawidek http://www.wheel.pl pjd_at_FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am!
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:51 UTC