Hi Bulat and others,

     Basically I am testing my Posix timer bindings. When a timer is created via timer_create( http://www.opengroup.org/onlinepubs/009695399/functions/timer_create.html), it is possible to pass a sigevent struct. When I specify sigev_notify as NONE OR SIGNAL, all is well. When I specify sigev_notify as THREAD which causes a callback to a Haskell function that I specify, then sometimes I get a core dump due to SIGABRT or an internal error in the Haskell run time library. Many times when I run as sigev_notify==THREAD every thing seems to be OK. I am trying to come up with ideas of what is wrong. I know there are constraints on what can be called from a sigevent callback function. Unfortunately I don't know anything about the ghc runtime model. ???

Vasili

On Mon, Jun 30, 2008 at 10:19 AM, Bulat Ziganshin <bulat.ziganshin@gmail.com> wrote:
Hello Vasili,

Sunday, June 29, 2008, 11:09:51 AM, you wrote:

>       When I run my test case, I get

> timer: internal error: scavenge: unimplemented/strange closure type 60 @ 0x76a28400

if you run low-level code that directly modifies memory via FFI
functions, it's more probable that error is just in your code

--
Best regards,
 Bulat                            mailto:Bulat.Ziganshin@gmail.com