On Mon, 5 Nov 2007, Nicholas Nethercote wrote: > This snapshot is strange: > > #----------- > snapshot=9 > #----------- > time=972 > mem_heap_B=900 > mem_heap_admin_B=72 > mem_stacks_B=0 > heap_tree=detailed > n1: 900 (heap allocation functions) malloc/new/new[], --alloc-fns, etc. > n1: 900 0xFE6737B: (within /lib/libc-2.6.1.so) > n1: 900 0xFE6759F: (below main) (in /lib/libc-2.6.1.so) > n0: 900 (heap allocation functions) malloc/new/new[], --alloc-fns, etc. > > > The last line is the problem, it shouldn't look like that. I'm using the > address 0 specially to refer to all the allocation functions. Could > VG_(get_StackTrace)() be returning 0 as an address at the bottom of the > stack trace? If so, I'll have to find a different way to encode the > allocation functions... maybe "(Addr)(-1L)".
Actually, that line shouldn't even be there, since Massif is supposed to ignore all stack frames below "main" or "(below main)". Hmm. Nick ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
