It took me some time to get back to this. I ran with the --dump-instr=yes option, and got the following output off PMPI_Recv:
fn=PMPI_Recv 0x5f870 0 48 0x5f875 0 48 0x5f87a 0 48 0x5f87d 0 48 0x5f882 0 48 0x5f887 0 48 ..etc fn=PMPI_Recv 0x1d1a6 1047 48 0x1d1a7 1047 48 0x1d1aa 1047 48 ...etc I presume this is what you were referring to? Any further suggestions? Best, Evan On Mon, Jun 15, 2009 at 5:01 PM, Josef Weidendorfer < josef.weidendor...@gmx.de> wrote: > On Monday 15 June 2009, Evan wrote: > > > It means that the debug reader in Valgrind was not able to detect > > > a symbol name for a given instruction address, ie. debug info seems > > > to be missing. This has nothing to do with missing command line > > > options. Build your program with debug info. > > > > > > > I should have said that I am building with debug info, and some names > > come back hex while others do not. For instance: > > ----------------------- > > fn=orte_gpr_replica_init > > 0 20 > > > > fn=0x0000000000005c60 > > 0 6 > > ----------------------- > > > > are listed alongside one another. > > Any chance this is from a shared library without debug info? Then > only function names can be detected which are exported symbols (ie. which > can be called from the outside), internal ones would get you the hex > number. > > > > Are you saying there are multiple such entries with the same function > name? > > > KCachegrind's behavior then would be to sum up the costs (according to > > > the format definition). > > > However, I can not think of a reason why Callgrind should print costs > for > > > the same function multiple times in one dump. Do you have an example > > > when this happens? > > > > > > Here's an example: > > > > This entry occurs: > > > > ----------------------- > > fn=PMPI_Recv > > 0 61074 > > ----------------------- > > > > followed by this one: > > ----------------------- > > fn=PMPI_Recv > > 0 9477 > > Not sure about this one. > Theoretically, the same symbol could appear in multiple shared libs > (and linker does not complain because of a weak symbol?). > Running with "--dump-instr=yes" should print the instruction offsets > for above output. Can you check this out? > > Josef >
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
