From lalit@savvion.com  Thu Aug 31 03:28:53 2000
Received: from oahu.tdiinc.com (oahu.tdiinc.com [206.40.33.137])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id DAA28756
	for <prolog@swi.psy.uva.nl>; Thu, 31 Aug 2000 03:28:48 +0200 (MET DST)
Received: from neptune.tdiinc.com (lalit@neptune.tdiinc.com [10.1.4.46])
	by oahu.tdiinc.com (8.9.3/8.9.3) with ESMTP id SAA21387
	for <prolog@swi.psy.uva.nl>; Wed, 30 Aug 2000 18:29:32 -0700 (PDT)
Received: from localhost (lalit@localhost)
	by neptune.tdiinc.com (8.9.0/8.9.0) with ESMTP id SAA10476
	for <prolog@swi.psy.uva.nl>; Wed, 30 Aug 2000 18:28:25 -0700 (PDT)
X-Authentication-Warning: neptune.tdiinc.com: lalit owned process doing -bs
Date: Wed, 30 Aug 2000 18:28:25 -0700 (PDT)
From: Lalit Jain <lalit@savvion.com>
To: prolog@swi.psy.uva.nl
Subject: Prolog Out of Stack Error!
Message-ID: <Pine.GSO.4.21.0008301827440.23697-100000@neptune.tdiinc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hi:
I am running the Prolog engine within a Java RMI Server.
The Server processes the first request fine but always fails in the second
request after the Prolog engine crashes due to "Out of local stack".

The error dump is as follows:

ERROR: Out of local stack while not in Prolog!?
Assertion failed: 0, file ./pl-alloc.c, line 331
SIGABRT 6 abort (generated by abort(3) routine)
    si_signo [6]: ABRT
    si_errno [0]: 
    si_code [-1]: SI_LWP [pid: 10401, uid: 2160]
        stackpointer=EE64F3D8

Inconsistent thread : best efforts attempt (may fail)
"RMI TCP Connection(6)-10.1.4.46" (TID:0x5b7bd8, sys_thread_t:0x5b7b18,
state:R, thread_t: t@16, threadID:0xee651dd8, stack_bottom:0xee652000,
stack_size:0x20000) prio=5 *current thread*

Does anybody have a clue as to what might be wrong?
What could be the potential cause for Prolog's " ERROR: Out of local stack
while not in Prolog!? ". 

Thanks,
Lalit

---							
Lalit Kumar Jain	SavVion Inc.
@ 408-330-3431		http://www.savVion.com
---			



