threading model: multi-threaded status: process terminated by SIGSEGV (Segmentation Fault) >
-----Original Message----- From: ext James Carlson [mailto:james.d.carl...@sun.com] Sent: Tuesday, March 17, 2009 1:08 PM To: Pavesi, Valdemar (NSN - US/Boca Raton) Cc: mdb-discuss at opensolaris.org Subject: RE: [mdb-discuss] How can libumem detect that a global variable wasdeleted? Pavesi, Valdemar (NSN - US/Boca Raton) writes: > I have a full core , and libumem does not show us the corruption by > ::umem_status Then it's possible that memory isn't actually corrupted. > > $C > fffffd7fffdea360 libc.so.1`strlen+0x40() > fffffd7fffdea4c0 libc.so.1`sprintf+0xcd() What does ::status say? Is it possible that you just have a plain old NULL pointer passed to %s here, and not any sort of memory corruption? -- 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
