|
From: Julian S. <js...@ac...> - 2007-03-21 11:27:55
|
I'm confused. So you're saying that Valgrind's handling of dynamic symbol tables is wrong? On Wednesday 21 March 2007 11:02, Josef Weidendorfer wrote: > Hi, > > [BTW, I am not not subscribed to this mailing list, and > I added valgrind developers mailing list to CC] > > > On Fri, Mar 16, 2007 at 11:35:53PM +0100, Josef Weidendorfer wrote: > > > Obviously, on my OpenSuse 10.2, libz.so is stripped and does not have a > > > symbol table, so opreport only shows the sum for all functions in the > > > library. However, Valgrind also loads the dynamic symbol table, so that > > > cachegrinds report showed the different functions in libz.so. > > > > Which is a fundamental error. The dynsym by its very nature does not > > have unexported symbols, fine > > so any samples taken against those symbols will > > be erroneously reported against the wrong symbol. I don't follow the implication. dynsym may not have unexported symbols, but what does that have to do with whether or not symbols have proper size/length information? J |