James, My problem was the global variable gHomeDnCacheList that was deleted. I saw a lot of corruptions that was detected by libumem. I was just trying to understand why it cannot be detected by libumem ,but now it is clear.
I am trying to use watchmalloc.so.1 > set | grep MALL MALLOC_DEBUG=WATCH,RW > set | grep UME UMEM_DEBUG=default,verbose UMEM_LOGGING=transaction,contents Thanks! Valdemar -----Original Message----- From: ext James Carlson [mailto:james.d.carl...@sun.com] Sent: Tuesday, March 17, 2009 11:19 AM 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: > Thanks, we had this problem , when It was hard to found out . What problem? Are you trying to determine whether a given static storage duration variable in your program (a global or static) is unused? If so, then that's a job for a static checker -- something like "lint." libumem can't help; it's unrelated to the task at hand because those variables are allocated during compilation time, not during run time. Are you trying to find dynamic storage that's ordinarily pointed to by global variables but is being leaked? If so, then that's something libumem+mdb can do. -- 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
