On 09-09-13 08:27, Thomas Raschbacher wrote:
>> write(13, "Q", 1) = -1 EAGAIN (Resource
>> temporarily unavailable)
>> read(25, 0x1843e70, 11) = -1 EAGAIN (Resource
>> temporarily unavailable)
Thomas,
could you please test 4c23432cc270554557f9e130331214d81164131b
I've put a mutex lock around the file-handle involved here, since read
and write are not thread-safe, and both actions here can (and will)
happen in different threads.
The only scenario I could come up with is:
Worker thread starts writing to filehandle 13 (the selfpipe). This
triggers a read-event in the main thread even before the worker has
finished writing, causing both of them to be unable to finish the call.
If this hypothesis is correct, this should be solved be mentioned commit
ID. And anyway, I doesn't hurt to protect the self-pipe handles with a lock.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
