Re: how to track down out-of-bounds error?

David Roundy writes:

The problem is trying to figure out where I'm doing this. Unfortunately, I have only been able to see this error on a rather large test repository, where it takes seven minutes for the test to show up.

Hah! *My* program can take hours before it crashes.

Any suggestions how I might most easily track this bug down?

Did you try compiling with -prof -auto-all, and running with +RTS -xc? -kzm -- If I haven't seen further, it is by standing in the footprints of giants