From jan@swi.psy.uva.nl  Wed May 31 13:54:39 2000
Received: from gollem.swi.psy.uva.nl (root@gollem [145.18.152.30])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id NAA04246;
	Wed, 31 May 2000 13:54:38 +0200 (MET DST)
Received: (from jan@localhost)
	by gollem.swi.psy.uva.nl (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id NAA19179;
	Wed, 31 May 2000 13:55:11 +0200
Date: Wed, 31 May 2000 13:55:11 +0200
Message-Id: <200005311155.NAA19179@gollem.swi.psy.uva.nl>
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Subject: Re: Exception segv
To: Rolf Socher <socher@fho-emden.de>, prolog@swi.psy.uva.nl,
        socher@fho-emden.de
In-Reply-To: Rolf Socher's message of Wed, 31 May 2000 12:53:39 -0500
Phone: +31 - 20 - 525 6121

> Can anyone help me with the following problem: 
> 
> >  ERROR: '$call'/1: Caught signal 11 (segv)
> >     Exception: (8) throw(error(signal(segv, 11), context('$call'/1, _G239))) ? 
> 
> What does the error message mean and how can the error be avoided? 

It means Prolog caught a segmentation violation (General Protection
Fault in MS-Jargon) while running $call/1. $call/1 is used to deal with
complex meta-calling (i.e. call(X) where X is a complex body-term,
something new in the 3.3.x versions).

A bug in this code was fixed in 3.3.5, so if you have an older version,
please upgrade.  If you have 3.3.6, contact me to reproduce the problem
here.

	Regards --- Jan

