Date: Thu, 9 Feb 2006 22:55:14 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Yar Tikhiy <yar@comp.chem.msu.su>, freebsd-current@freebsd.org Subject: Re: memguard monitoring of more than 1 memory_type? Message-ID: <20060209215513.GA3590@garage.freebsd.pl> In-Reply-To: <20060207191408.GA50909@troutmask.apl.washington.edu> References: <20060207183152.GA50629@troutmask.apl.washington.edu> <20060207190121.GF19674@comp.chem.msu.su> <20060207191408.GA50909@troutmask.apl.washington.edu>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Feb 07, 2006 at 11:14:08AM -0800, Steve Kargl wrote: +> On Tue, Feb 07, 2006 at 10:01:21PM +0300, Yar Tikhiy wrote: +> > On Tue, Feb 07, 2006 at 10:31:52AM -0800, Steve Kargl wrote: +> > > Can memguard monitor the usage of more that one memory_type? +> > +> > From the memguard(9) manpage: +> > +> > Currently, MemGuard can only take over malloc(), realloc() and free() for +> > a particular malloc type. +> +> Thanks for pointing out the obvious. I've read that manpage several +> times and somehow missed the word "particular". It's unfortunate +> that it can't monitor more than one type of memory allocation because +> the new pts code has either uncovered a latent bug in devfs or the +> pts patch is stomping on memory. It shouldn't be hard to implement. You need to change function memguard_cmp() in sys/vm/memguard.c, which decides which memory type should be monitored. -- 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) iD8DBQFD67pBForvXbEpPzQRAr1GAKCiKlR/9iMRlgDnd5g3g5HlttVONwCgjkAY Y7ukj6N+jqSwEXo/0sm0Myk= =11Gg -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060209215513.GA3590>