mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-04 18:56:10 +00:00
4eac75bf3e
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