memguard monitoring of more than 1 memory_type?
Pawel Jakub Dawidek
pjd at FreeBSD.org
Thu Feb 9 13:55:51 PST 2006
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 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
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20060209/6bdb7381/attachment.bin
More information about the freebsd-current
mailing list