
21 Jan
2008
21 Jan
'08
10:28 a.m.
On Sat, Jan 19, 2008 at 08:36:55PM +0100, Alfonso Acosta wrote:
On Jan 19, 2008 2:36 PM, David Roundy
wrote: Using ghc 6.6, but I've since isolated the bug as being unrelated to the IORefs and threading, it was in an FFI binding that somehow never died until I was testing this new code.
In case the you are creating a binding of haskell code. Did you make sure that the runtime constructor and destructor (hs_* functions) are properly called? The could be the source of the segfault.
No, there are no bindings to haskell code involved. Perhaps it's even a segfault in libwww itself. -- David Roundy Department of Physics Oregon State University