Re: SIGALRM, SIGVTALRM, and third party libraries

2010-09-03 Thread Bryan O'Sullivan
On Fri, Sep 3, 2010 at 2:13 PM, Edward Z. Yang wrote: > > I think the primary downside is that it's not portable (yet) to Windows. That's fine, assuming that blocking those signals doesn't cause some more catastrophic failure. My current narrow need is for code that works on the platforms I act

Re: SIGALRM, SIGVTALRM, and third party libraries

2010-09-03 Thread Edward Z. Yang
Excerpts from Bryan O'Sullivan's message of Fri Sep 03 17:00:03 -0400 2010: > What I am wondering is if there's a practical downside to doing this. Am I > going to accidentally kill something? This is a very important gap in the > usability of GHC with native libraries, and if this approach actuall

SIGALRM, SIGVTALRM, and third party libraries

2010-09-03 Thread Bryan O'Sullivan
I spent some time this morning trying to use HDBC-mysql to talk to a database. It uses the C mysql bindings, which talks over a blocking socket to the database server. Not surprisingly, it fails reliably when the thread it's running in is hit by an RTS-initiated alarm signal. I've managed to make