Re: Memory problem using Centaur1.2

[td@almeria.inria.fr (Thierry Despeyroux)]

In article <1995Jan26.092448.21556@sophia.inria.fr>, parisel@enseeiht.fr (Christophe PARISEL) writes:

|>   I have a problem with PROLOG, when running a TYPOL interpretation
|> on 'rather heavy' sources on Centaur1.2 : 
|>   A 'MU-PROLOG : out of memory error' is raised whichever memory
|> parameter [1] is used when running 'centaur+' , and always occurs at the
|> same time.
|> Is it a problem of garbage-collector bad configuration or something
|> like that?

|> [1] The highest parameter I've been using is 2300.


The parameter that is given to the command "centaur" is the size
of the lisp "cons" zone. This is not your problem since it is the
prolog stack that is too small.

Assuming that the probleme is not a loop during the prolog execution,
you may 
- reconfigure and recompile your centaur+ to use a bigger prolog
  (GSTKLEN is the variable used for this)
- try to optimize you Typol (for example, if you are sure that a 
  predicate is deterministic you can use once(<sequent>) to recover
  the place that is used in the stack
- use Centaur2.0 that uses Eclipse in place of MU-Prolog. Eclipse
  enlarge its stack dynamically until all your swap space is
  used, and uses a garbage collector.

-- 
Send contributions and compliments to centaur@sophia.inria.fr. Registration
and administrative matters should be sent to centaur-request@sophia.inria.fr.
+---------------------------------------------------------------------------+
|     Thierry Despeyroux      | email: Thierry.Despeyroux@sophia.inria.fr   |
| I.N.R.I.A. Sophia-Antipolis | phone: +33 93 65 77 07 fax: +33 93 65 77 66 |
+---------------------------------------------------------------------------+