From jan@swi.psy.uva.nl  Fri Nov 26 09:55:33 1999
Received: from gollem.swi.psy.uva.nl (root@gollem [145.18.114.15])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id JAA04731
	for <prolog@swi.psy.uva.nl>; Fri, 26 Nov 1999 09:55:33 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]])
	by gollem.swi.psy.uva.nl (8.9.3/8.9.3) id JAA28170
	for prolog@swi.psy.uva.nl; Fri, 26 Nov 1999 09:55:57 +0100
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Organization: SWI, University of Amsterdam
To: prolog@swi.psy.uva.nl
Subject: Re: Cryptic Error Message
Date: Fri, 26 Nov 1999 09:51:57 +0100
X-Mailer: KMail [version 1.0.21]
Content-Type: text/plain
References: <E713F2760348D211A9B600805F6FA1AB035598BF@RED-MSG-09.itg-messaging.redmond.corp.microsoft.com>
MIME-Version: 1.0
Message-Id: <99112609555700.28132@gollem>
Content-Transfer-Encoding: 8bit

On Fri, 26 Nov 1999, Douglas Miles (Volt Computer) wrote:
>what does error mean?
>
>[nobody@www library]$ ./mypl.runtime
>
>[WARNING: Out of local stack while not in Prolog!?]
>pl: pl-alloc.c:218: outOfStack: Assertion `0' failed.

In most cases this is a segmentation fault that is misinterpreded
as a stack-overflow.  What to do next?

For debugging this type of error, it is a good idea to make a
Prolog that does not handle stack-overflows using segmentation
faults using

	./configure <options> --disable-segv-handling

and next run prolog under the C-debugger.  If all functions
properly you can revert to the segv-handing based stack guarding.

	Regards --- Jan

