Segfaulting programs with GHC 6.4.1

John Goerzen jgoerzen at
Fri Oct 21 10:15:44 EDT 2005

On Fri, Oct 21, 2005 at 03:17:34PM +0200, Krasimir Angelov wrote:
> If I remember exactly you said that your program was working before
> movement to ghc 6.4.1. If that is the case then I doubt that the
> problem is in HSQL. In any case the easy way to catch that is to add
> some trace messages in HSQL. At least traces at the beginning and at

Unfortunately, this has been elusive so far, perhaps due to the
multithreaded nature of the program.  It appears to be crashing at
different places different times -- after calling fetch one time, in the
middle of query the next.  I am trying to narrow it down a bit by
reducing the number of threads and hoping I can still duplicate the
problem in a reasonable amount of time.

I should also add that I'm putting these debug statements in the
PostgreSQL module, but I had observed these segfaults previously when I
was using Sqlite3.  I switched from sqlite3 to postgresql both for
performance reasons, and to try to narrow down this problem.  It helped
with the performance, anyway ;-)

-- John

More information about the Glasgow-haskell-users mailing list