[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gcl-devel] Re: value stack overflow
From: |
Matt Kaufmann |
Subject: |
[Gcl-devel] Re: value stack overflow |
Date: |
Thu, 11 Dec 2003 13:55:18 -0600 |
Bill --
Camm Maguire's reply will help you if you want to debug in raw Lisp (GCL).
(Thanks, Camm!) Alternatively, you could try first executing (in the ACL2
loop):
(brr nil)
Then, after the stack overflow:
:q ; quit out of the break
:q ; exit the ACL2 loop
(cw-gstack *deep-gstack* state)
With luck, this will show you looping rewrite rules.
See also the documentation topic CW-GSTACK.
-- Matt
cc: address@hidden, address@hidden
From: "Camm Maguire" <address@hidden>
Date: 11 Dec 2003 14:51:57 -0500
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Reply-to: address@hidden
Sender: address@hidden
X-Listprocessor-Version: 8.2.10/020311/17:52 -- ListProc(tm) by CREN
X-WSS-ID: 13C6149B397667-01-01
Content-Type: text/plain;
charset=us-ascii
Greetings!
You can see what is on the stack with :vs. You can see a backtrace
(if that is helpful) with :bt. You can jump to any frame with :fr,
and see local variables with :bl.
If there is in fact no bug and you just need a bigger stack, at the
gcl toplevel, you can try (setq si::*multiply-stacks* 2) to double the
stack size, (si::save-system "new_image"), and then try executing
again with new_image.
Take care,
address@hidden writes:
> Can someone remind me what's the most useful thing to do to debug a
> value stack overflow. I've looked at several of the options under :h,
> but I can't really see what's going on.
>
> Error: Value stack overflow.
> Fast links are on: do (si::use-fast-links nil) for debugging
> Error signalled by ACL2-PC::PROVE.
> Broken at COND. Type :H for Help.
>
>
> Bill
>
>
>
--
Camm Maguire address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah