From a-doug@microsoft.com  Fri Nov 26 11:42:43 1999
Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121])
	by swi.psy.uva.nl (8.9.3/8.9.3) with SMTP id LAA07912
	for <prolog@swi.psy.uva.nl>; Fri, 26 Nov 1999 11:42:42 +0100 (MET)
Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 26 Nov 1999 02:42:36 -0800 (Pacific Standard Time)
Received: by INET-IMC-05 with Internet Mail Service (5.5.2650.21)
	id <XN42KCH6>; Fri, 26 Nov 1999 02:42:35 -0800
Message-ID: <E713F2760348D211A9B600805F6FA1AB035598C0@RED-MSG-09.itg-messaging.redmond.corp.microsoft.com>
From: "Douglas Miles (Volt Computer)" <a-doug@microsoft.com>
To: "'prolog@swi.psy.uva.nl'" <prolog@swi.psy.uva.nl>
Subject: RE: Cryptic Error Message
Date: Fri, 26 Nov 1999 02:42:56 -0800
X-Mailer: Internet Mail Service (5.5.2650.21)

I figured I would upgrade to 3.3.0 beta upon this error.. and see if that
would help.

It did.. Then though maybe it was probably just my overheated cpu :)... 
Or bad NIC card.. cause the box locked up an hour later. 

So after getting 3.3.0 working I am now upgrading the ~swi/library
I had not realized how much I edited it up.. adding functions allot..
Wondering which of the ~swi/library files are new in 3.3.0?
And only make required changes to my old ones.

I wanted to mention I like the "%" in
 %  quintus compiled into quintus 0.01 sec, 11,580 bytes

Have a prolog program that communicates entirely over sockets (the tcp.tgz
from /ALPHA) and trying
 to use write, listing.. all that is stdout messages.. 
I want to change the stderr and stdout to a function like ...
... all writing to call the clauses
mystderr(X)...
mystdout(X)...

Thank you, 
[mailto:a-doug@microsoft.com]


-----Original Message-----
From: Jan Wielemaker [mailto:jan@swi.psy.uva.nl]
Sent: Friday, November 26, 1999 12:52 AM
To: prolog@swi.psy.uva.nl
Subject: Re: Cryptic Error Message


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

