On 07 November 2005 14:16, Joel Reymont wrote:

Well, I was suspecting FPS but I removed all FPS usage and went with regular lists. The program still crashes. I did not see a "malloc: memory exhausted" error from ghci this time, it just crashed with an application error while writing to some random memory location.

I built a separate exe (this is Windows) and ran it in gdb for a segmentation violation in with this stack trace:

?? () s7yw_info () ?? ()

If you are pretty certain that you aren't doing anything unsafe, then this is a bug in GHCi. If you can provide us with a reproducible test case, I'll look into it. Cheers, Simon