On Wed, Aug 10, 2005 at 03:51:21PM -0700, john liu wrote:
> Thanks Dan,
>
> I guess the reason is that the flag for 8192 cache is
> reset to 0x269, note 0x9 not 0xf. 0x9 does not have
> the redzone buf set.
>
> Other caches having 0x22f as the flag.
0x269 indicates KMF_FIREWALL (0x40); there is
Thanks Dan,
I guess the reason is that the flag for 8192 cache is
reset to 0x269, note 0x9 not 0xf. 0x9 does not have
the redzone buf set.
Other caches having 0x22f as the flag.
john
--- Dan Price wrote:
> On Wed 10 Aug 2005 at 03:00PM, Qiang Liu wrote:
> > > 03065b88::kmem_verify
>
On Wed 10 Aug 2005 at 03:00PM, Qiang Liu wrote:
> > 03065b88::kmem_verify
> Summary for cache 'kmem_alloc_2688'
> clean
> > 03068288::kmem_verify
> mdb: cache 3068288 (kmem_alloc_8192) does not have redzone
> checking enabled
And I'm not sure what the answer is for the kmem_a
On Wed 10 Aug 2005 at 03:00PM, Qiang Liu wrote:
> >
> > 3001827e880::kmem_verify
> mdb: cache 3001827e880 () does not have redzone checking enabled
Right. You can't kmem_verify a buffer, only a whole kmem_cache. So
do this:
::kmem_cache
Then locate the address of the cache you are interested i
# uname -a
SunOS pumba 5.10 Generic sun4u sparc SUNW,Sun-Fire-280R
# ls -l
total 1271762
-rw-r--r-- 1 root root 2 Aug 8 10:26 bounds
-rw-r--r-- 1 root root 677312 Aug 10 10:08 my.so
-rw-r--r-- 1 root root 1163675 Aug 8 10:26 unix.2
-rw-r--r-- 1 root root
BTW
I do have kmem_flags=0x3f in /etc/system
This message posted from opensolaris.org
