|
From: Josef W. <Jos...@gm...> - 2007-06-05 08:57:06
|
On Monday 04 June 2007, Jason Lustig wrote: > I am trying to use valgrind to profile my webserver setup to increase > its load capacity, but when I try to exit the program (using control > +c) nothing happens and I have to kill -s 9 valgrind in order to get > it to stop - which is no good since then I don't get any output in > the callfile. Why would this be happening? Actually, I have no idea. For callgrind, you should be able to control the run from the outside with callgrind_control. Does e.g. "callgrind_control -b" print something? If not, it really is hanging somewhere... If callgrind_control is working, you can dump the profile data with "callgrind_control -d" to work around the fact that Ctrl-C is ignored. > The command I'm running is: > > # valgrind --tool=callgrind --dump-instr=yes --trace-jump=yes -v /usr/ > local/apache2/bin/httpd -X > > And the last items to come up in the verbose output (to stdout) are > >from the PHP extensions loading: > > --8738-- Reading syms from /usr/local/lib/php/extensions/apc.so > (0x4751000) > --8738-- Reading syms from /usr/local/lib/php/extensions/pdo.so > (0x4768000) > --8738-- Reading syms from /usr/local/lib/php/extensions/pdo_pgsql.so > (0x4004000) > --8738-- Reading syms from /usr/local/pgsql/lib/libpq.so.5.0 (0x477D000) > > Then it just hangs, and when I hit control+c nothing happens. > > I already tried removing some of the extensions but nothing seems to > be working. Any thoughts? > > Here's some server info, which could perhaps help: > > # valgrind --version > valgrind-3.2.3 > > # callgrind --version > callgrind-0.10.1 That is an old stale version of callgrind still installed on your system. You can remove it, as callgrind is merged into VG since 3.1. However, it is not used as you start with "valgrind ...". > > # uname -a > Linux HOSTNAME 2.6.15-1.2054_FC5smp #1 SMP Tue Mar 14 16:05:46 EST > 2006 i686 i686 i386 GNU/Linux > > Thanks, > Jason > > |