On Dec 13, 2005, at 11:57 PM, Jon Weston-Dawkes wrote:
In version 5.5.40, I encounter the following error message when I
run my SWI-Prolog application:
[FATAL ERROR:
Received signal 11 (segv) while in 15-th garbage
collection]
With the same memory settings (16M, 64M, 16M for local, global,
trail stacks respectively) within SWI-Prolog-Editor, the same
application runs without error. This particular app must explore a
very large search space and has the potential for significant
backtracking.
Any ideas on the source of the problem?
If Prolog crashes on a clean Prolog program there is a bug in the
system. So, if possible, please
send me the program with instructions. Normally such problems are
fixed quickly if I can reproduce
them, but this time I'm a bit too busy for that.
To keep going you may try to use different stack limits. That may
change the timing of garbage
collection. Of course it doesn't feel very safe :-)
I've seen more messages that using teh SWI-Prolog editor or not makes
a difference. In most
cases it are things that do not work with it though. Still doesn't
feel good :-(
Cheers --- Jan
|
