Jonathan Adams writes: > On Thu, Feb 26, 2009 at 09:07:00PM +0100, max at bruningsystems.com wrote: > > There is a redzone page at the low end of all(?) kernel stacks. When it > > is touched, > > the system panics (better than overwriting other memory). > > See the code for segkp_fault(0 in uts/common/vm/seg_kp.c. > > But kmdb has it's own stacks. I don't know if they have redzone pages.
Even if they do, they're not so likely to catch an accidental use of a 512K structure (64K array of 8 byte pointers, if you're curious) on the stack. You'll just hop the redzone and land, well, whereever you land. In my case, it seemed to be part of the heap used by umem inside kmdb. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
