> 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. > 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 cob=/usr/lib/openmpi/lib/openmpi/mca_pml_ob1.so cfi=??? cfn=mca_pml_ob1_recv calls=1053 0 0 44144882 0 17901 ----------------------- I should also possibly have mentioned that I'm working with MPI, though it's unclear to me how that would cause this. Best, Evan ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
