[Valgrind-users] Signal handling and delivery of siginfo_t

[Raymond R. <ra...@co...>]

Hello,
	I have just recently started using valgrind and, I must
add, am impressed - the sheer audacity of the approach is great.
(Thanks to Messrs. Seward and Nethercote, and all the developers.)

I would like to use it on a program I have that does asynchronous
I/O without using select().  It registers a signal handler using
sigaction and, on receipt of SIGIO, extracts the file descriptor
that caused the signal from its second siginfo_t * argument.
Since valgrind passes a NULL pointer to applications when invoking
signal handlers, my program simply segfaults in its handler.


My question is this:  are there any plans to change the signal
handling to support the propagation of the siginfo_t * supplied by
the kernel to the application?  I am guessing that to do so would
be a fair bit of work.  Am I wrong is thinking that valgrind only
maintains a pending flag for each signal, rather than a true queue
of signals like the kernel does?

If this is in the works, I'd be interested to help if I can.  If
not, I'd be happy to start it.  Either way, who should I talk to
about this?


Regards,
	Raymond.