[xmonad] [process] Fixed asynchronous exception bugs in readProcess and readProcessWithExitCode
Bas van Dijk
v.dijk.bas at gmail.com
Fri Jan 13 14:17:26 CET 2012
On 12 January 2012 23:14, Brandon Allbery <allbery.b at gmail.com> wrote:
> On Thu, Jan 12, 2012 at 14:35, Bas van Dijk <v.dijk.bas at gmail.com> wrote:
>> 2) If an asynchronous exception was thrown to the
>> stdout/stderr-read-thread it did not execute the putMVar anymore
>> resulting in a dead-lock when takeMVar was executed.
> Hah. I knew something like this was in there; xmonad is hanging instead of
> catching an exception or signal when the far end of a pipe (usually xmobar)
> goes away.
It's good to hear that these fixes can actually solve a real problem :-)
BTW I updated the patch in the ticket because I forgot to 'restore'
the masking state in the IO processing code.
More information about the xmonad