Geek asks and answers

Callgrind with spawn-fcgi does not create profiling data

I need to profile my C ++ application that starts with spawn-fcgi. I tried using callgrind, but the output of callgrind in KCachegrind does not show any information about my applications.

valgrind --tool=callgrind --dump-instr=yes --simulate-cache=yes --collect-jumps=yes --demangle=no --trace-children=yes --callgrind-out-file=%p spawn-fcgi -s /tmp/sock.tmp ./myApp arg1 arg2

This command creates two files 10012 and 10013, but the second file is empty. The first file contains overhead location information for spawn-fcgi, ld-2. *. So amd libc.

Please suggest the correct option for obtaining profiling information for my application.

+3
source share
1 answer

I experienced a similar behavior when the profiled fastcgi process crashed on exit (therefore, statistics are not reset when terminated with SIGSEGV).

callgrind_control :

callgrind_control --dump

callgrind_control -i off, callgrind_control -i on, reset callgrind_control -z.

. callgrind_control http://valgrind.org/docs/manual/cl-manual.html.

+2

More articles:


All Articles