Re: [Valgrind-users] callgrind.out file size is zero

[Floyd, P. <pj...@wa...>]

On 18/10/2022 14:54, Mahin Pandya wrote:
>
> Hi All,
>
> I am tying to use Valgrind to generate code profiling, generated 
> callgrind.out.2199511 file is of zero size. After enabling the debug 
> log below message is displayed:
>
> ...
>
> ==== SB 2759 (evchecks 30598) [tid 1] 0x415b170 execve 
> /usr/lib/x86_64-linux-gnu/libc-2.31.so+0xe3170
>
> --1314389:1: syswrap Exec of /devsrc/wineinst/bin/wine64-preloader
>
> --1314389:1: gdbsrv remote_finish (reason orderly_finish) 1030 -1
>
> --1314389:1: gdbsrv 1314389 (creator 1314389) maybe unlinking
>
> ...
>
> Any idea why it does not generate profiling data? I am new to 
> Valgrind, so not sure may have missed obvious things. Any 
> pointers/suggestion are welcome.
>
> Thanking you.
>
> regards,
>
> Mahin
>

Hi

My guess is that your process is doing a fork/exec (or maybe just an exec).

Try with --trace-children=yes

I'd also recommend that you start with --tool=none before moving on to 
callgrind.

A+

Paul