|
From: pkr <pan...@ya...> - 2004-08-20 12:12:31
|
Not sure whether this is possible in valgrind.... 1. But can we not trap signal(), sigaction() calls (similar to trapping malloc etc) to register the user function ptr in a internal data structure and then on the actual signal we do our job and then call user function ? 2. And then the signal number can always be cmdline parameter so that user is free to select a appropriate signal (some of them are unused ie SIGUSR1 etc) and then user is also warned that this signal wont be passed to the program.. Thanks, Pankaj Tom Hughes wrote: > In message <412...@ya...> > pkr <pan...@ya...> wrote: > > >>My intention was about leak report only. It would be good to have >>some way of notifying (signal) valgrind to generate the report. >>As there could be situations when the above api cant be inserted in >>the code... > > > The problem is that if valgrind starting acting on signals it > would break programs which used that signal themselves - there > is no separate valgrind process to send the signal to. > > Tom > |