[Valgrind-users] Bug with Callgrind and Trace-children

[kapil a. <kap...@gm...>]

Hi all,

I am using valgrind with callgrind tool under wine but facing a few
problems. I am using following command to run valgrind

valgrind --tool=callgrind --trace-children=yes --dump-instr=yes
 --trace-jump=yes --separate-threads=yes  wine <program> <args>

Since I have given --dump-instr=yes, I am trying to visualize the time
spent in each instruction. However, when I try to analyze this through
kcachegrind, the Machine code section does not show the disassembly. The
error message shows that input to "objdump" is not correct, the path to
current folder is actually being passed as input to  objdump instead of
input file. The valgrind is producing callgrind out-file but the name of
<program> is missing in the callgrind-out file. I compared it with
callgrind.out from a correct program and noticed that the place where the
name of the file should have been specified is actually empty. Thus ,
objdump inside kcachegrind is try to disassemble some garbage location.

Any idea whether I am missing some option?

--Kapil