Hello, I've been trying to use valgrind v3.6.0 to debug a cross-compiled Power-PC application. I believe I built valgrind correctly, using the two-stage build procedure: ./valgrind --version valgrind-3.6.0
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) I checked using ps that the application was not yet started when valgrind terminated. I used the command: ./valgrind -v --tool=memcheck --leak-check=yes <application> I have attached the full transcript output: http://old.nabble.com/file/p30891730/valgrind.log valgrind.log Can anyone help? Many thanks, Paul -- View this message in context: http://old.nabble.com/Process-terminating-with-default-action-of-signal-14-%28SIGALRM%29-tp30891730p30891730.html Sent from the Valgrind - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
