> Probably a stack overflow which, unfortunately, causes Hugs=20 > to segfault. I presume this is the C stack overflowing, right? One possibility, albeit a very non-portable one, to catch SIGSEGV and make a good guess as to whether it was caused by a stack overflow or not. Generating a beter error message in this case might help eliminate a few bug reports... Cheers, Simon