On 10/02/11 14:10, ppmoore wrote:
> The signal SIGALRM is handled in the main constructor for the application,
> invoked from main(), so I thought that this should be sufficiently quick.
>
> if (signal(SIGALRM, &signalHandler) == SIG_ERR)
> {
> log_printf(LOG_ERR, "Signal when registering SIGALRM
> handler\n");
> return -1;
> }
The important question is not just where that is, but where the code
that arranges for the SIGALRM to be sent is relative to that. It should
be after that code not before it basically.
> IS there a way top change the default signal-handling in valgrind?
No, any more than there is any way to change the kernel's signal
handling when you are running outside valgrind.
Valgrind is only doing exactly what the kernel would normally do - the
only difference is that your program is probably running more slowly
because it is running under valgrind.
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
