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

[Philippe W. <phi...@sk...>]

As a wild guess: looks like your application is doing fork and exec.
You might try to add then  --trace-children=yes 
  (and possibly if needed you should use --trace-children-skip=...... if tracing
   all children is too much).

Otherwise, try first with a very simple standalone program
e.g. something like:
   for (int i = 0; i < 1000; i++)
	printf ("hello world %d\n", i);

see if that works, and compare the debug trace of the very simple working
case with the more complex non working case.

Philippe


On Tue, 2022-10-18 at 12:54 +0000, 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
>  
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users