hi, On Fri, Jul 31, 2009 at 11:51 PM, Nicholas Nethercote<[email protected]> wrote: >> What I am really curious about is why the backtrace output by valgrind >> does not show the symbolic names of my functions. Would someone mind >> point me to the code in valgrind which performs symbol lookups so that >> I can figure out what I need to do in my loader to make at least this >> work ? > > It's in coregrind/m_debuginfo/. The FAQ also has a question relating > to stack traces that you might find helpful.
Just in case anyone ever stumbles upon similar problems, I tracked this down as coming from valgrind's di_notify_unmap which is overly aggressive in removing debug object descriptors from its global list. I re-arranged my code to produce the same memory mappings but with the mmap & munmap in a different order and its worked. i.e., when I do an munmap of a memory area backed by a debug object descriptor, this triggers its deletion, even when the munmap is really removing only a small part of the object memory mapping which is unused. I merely moved all munmaps to _before_ the mmaps to make sure that all debug object descriptors are created with the right memory mapping size from the start... It was fun to debug :) Mathieu -- Mathieu Lacage <[email protected]> ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
