On 10/02/11 13:21, ppmoore wrote: > The problem I have is that valgrind prematurely exits after about 10 > seconds: > ==624== Process terminating with default action of signal 14 (SIGALRM) > ==624== at 0xF9D5BA4: socket (in /lib/libc-2.3.2.so)
Termination is the default behaviour for SIGALRM so that is the expected behaviour if a SIGALRM is received. If I had to guess I would say you program is arranging for an alarm signal (probably with the alarm() function) before it has made arrangements to handle the resulting signal and, when running under valgrind, the alarm expires before it gets around to installing the signal handler. > I checked using ps that the application was not yet started when valgrind > terminated. How did you check that? The valgrind process *is* the application. Tom -- Tom Hughes ([email protected]) http://compton.nu/ ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
