inclusion of Network.Curl causes compiler issues and coredumps

[b7j0c]

the attached program began to show compiler failures (though not always reproducible), and coredumps (again, not always reproducible) once HXT was replaced with Text.XML.Light.

i have taken care to install (and reinstall) packages with cabal-install although many of the packages i use were originally installed with traditional Setup.hs installation and registry.

i'm really not sure what the issue is.

my environment is ghc-6.8.2 on freebsd7/i386. my ghc was installed from freebsd ports. i use cabal-install to manage other packages. this program is the only one i have had issues with. i am attaching the program in its entirety.

[b7j0c]

the failure-prone program in its entirety

[b7j0c]

i compiled this program with -debug and ran it through gdb, here is the output:

(gdb) run Starting program: /usr/home/brad/git/dev/haskell/newspage/newspage newspage: internal error: task 0x286040e0: main thread 1 has been GC'd

(GHC version 6.8.2 for i386_unknown_freebsd) Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug

Program received signal SIGABRT, Aborted. 0x283f3007 in kill () from /lib/libc.so.7

including network.curl maintainers

[b7j0c]

ignore above comments regarding hxt and text.xml.light, it is doubtful they are the issue

[dons]

$ ghc --make newspage.hs 
[1 of 1] Compiling Main             ( newspage.hs, newspage.o )
Linking newspage ...

$ ./newspage 
newspage: internal error: task 0xda5c30: main thread 1 has been GC'd
    (GHC version 6.8.2 for x86_64_unknown_linux)
    Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
zsh: abort      ./newspage

Now, the curl library uses finalisers and MVars to manage resources. I wonder if this is a finaliser issue.

[simonmar]

the program currently hangs for me waiting for a response from download.finance.yahoo.com. I'll try again later.

[simonmar]

I've been unable to reproduce this on x86-64-Linux (however I did find a problem with the curl library and GHC 6.10 which I've fixed, so it wasn't a completely pointless exercise).

Lacking a way to reproduce this we'll have to close the ticket and hope if the bug still exists that it resurfaces later.