|
From: Justace C. <pro...@co...> - 2005-07-12 13:35:52
|
Well, I looked at the actual binary for the original program with "nm -a". I have included the output with this email, it is small enough. I have been able to cross reference a few of the hex numbers to symbols in the file. For example: 0x0804F304 -> main 0x0804F76C -> _ZN6TreffyC1Ev 0x0804FA84 -> _ZV6Treffy4TestEv These correspond to the functions main, Treffy constructor, and Treffy::Test. So it seems that there is some name mangling. Does this help to shed light on the problem? Thanks for the help... Justace On Tue, 2005-07-12 at 11:54 +0200, Josef Weidendorfer wrote: > Hi, > > On Tuesday 12 July 2005 00:09, Justace Clutter wrote: > > Valgrinders... > > > > I was working on a program and then decided to look into using > > kcachegrind to help me profile and generate call graphs. When running I > > noticed that there was a bunch of numbers where I thought there should > > have been function or method names. I looked everywhere I could and can > > not find a way to fix the problem. So, I wrote a very small and silly > > program to see if that would fix it, nope, same problem. I am using gcc > > 3.4.4 on Gentoo and using the "-ggdb" flag only for my compiles and > > links. > > Sorry, I just can not see your problem in the small test you provided. The > only thing I see is that system libraries on your system are stripped. > If you look only at the symbols from your binary (Grouping by ELF object, > select "test"), almost all entries in the list have function names and are > not hex numbers. So your compiler is producing the debug info, and valgrind > is loading this info. The entries without names are compiler generated > without symbol info. > > Regarding the screen shot, it actually looks like there are quite a few > functions without symbol info. Either the compiler does not provide debug > info (seems unlikely), the binary is somehow stripped afterwards (you should > recheck with "nm" if expected symbols are actually provided in the binary), > or the valgrind debug info reader is buggy. > > Unfortunately I can not reproduce the problem, and as said above, the small > test code seems fine. Can you give me a hex number there where a symbol name > (from the "test" binary) should show up? Or generate a test case where you > can show this? > > Josef > > > I also tried a variety of combinations between -p, -pg, -g, > > -g3... I am including in this email a tarball of the test code to show > > what I mean along with with a picture of the desktop showing the > > offending program. I am really not sure where to go with this. The > > tools will be un-usable if I can not tell which functions are which. > > Thanks in advance for any help that you can provide. > > > > Justace clutter > > > > The attachements were too big so I posted them to a web address. > > > > http://clued0.fnal.gov/~prophecy/valgrind > > > > P.S. Sorry for the repost > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > > happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest > > in dual core and dual graphics technology at this free one hour event > > hosted by HP, AMD, and NVIDIA. To register visit > > http://www.hp.com/go/dualwebinar > > _______________________________________________ > > Valgrind-users mailing list > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |