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

[Josef W. <Jos...@gm...>]

Hi,

Am 14.06.2012 01:41, schrieb kapil anand:
> 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.

As workaround, you should be able to edit the profile dump file such
that the machine code view works.

It looks like a bug with forking. Can you raise a bug
report for it? Of course it would be cool if you can come up with
a short failing test case.

Thanks,
Josef

>
> Any idea whether I am missing some option?
>
> --Kapil
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users