tree bafe4b00aa0b61a7bf1bdedd5c32e79fae4112fa
parent d4266ed52c5b36166be2494bf0ab4b3630055308
author fitzhardinge <fitzhardinge@a5019735-40e9-0310-863c-91ae7b9d1cf9> 1068246588 +0000
committer fitzhardinge <fitzhardinge@a5019735-40e9-0310-863c-91ae7b9d1cf9> 1068246588 +0000

Fix some bugs in syscall/signal handling:

If the proxyLWP for a thread got a signal just as we were sending the
syscall request to it, then we would end up running the syscall twice.
The fix is to not check the results pipe while sending the syscall request
- wait until we're in a better state for handling signals (the deadlock
the results-read was supposed to avoid cannot actually happen).

Related to that, if we're delivering a signal to a thread, and that thread
is currently waiting for a syscall to complete, make sure we collect the
syscall results before entering the signal handler (otherwise we may end
up bogusly trying to restart the syscall by moving EIP back, even though
it now points to the signal handler rather than the syscall instruction)

This change also adds an assertion to VG_(restart_syscall) to make sure
we were actually restarting a syscall and not just randomly changing EIP
(this found the problem above).

Also, make set/getitimer run in the proxyLWP context, so that they
modify/read the proxyLWP's timers rather than the schedluer LWP's timers.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2013 a5019735-40e9-0310-863c-91ae7b9d1cf9