From: Yannick Lallement
Subject: backtrace while debugging?
Date: 
Message-ID: <uumafk3fy9v.fsf@bronto.soar.cs.cmu.edu>
Hi,

I would like to know if there is a way to know which function call
caused an error in lisp; sort of like obtaining the backtrace of the
calls that lead to the error, or at the very least which function call
caused the error.

To give an example, if I get:

Error: Index(s) to array function is/are out of the range of the array.
  [condition type: SIMPLE-ERROR]

how do I know which of my function called the array function? 

I'm using Allegro CL 4.2.beta2.0.

Thanks in advance,

Yannick
From: Michel GEORGE
Subject: Re: backtrace while debugging?
Date: 
Message-ID: <33BCBC38.7FBE@planisware.fr>
Yannick Lallement wrote:
> 
> Hi,
> 
> I would like to know if there is a way to know which function call
> caused an error in lisp; sort of like obtaining the backtrace of the
> calls that lead to the error, or at the very least which function call
> caused the error.
> 
> To give an example, if I get:
> 
> Error: Index(s) to array function is/are out of the range of the array.
>   [condition type: SIMPLE-ERROR]
> 
> how do I know which of my function called the array function?
> 
> I'm using Allegro CL 4.2.beta2.0.
> 
> Thanks in advance,
> 
> Yannick

When you are in the debugger you can use the :zoom (or :zo) command
which displays the calling stack. 
You can have the command list by using :help .
From: Thomas A. Russ
Subject: Re: backtrace while debugging?
Date: 
Message-ID: <ymin2nyyhdm.fsf@sevak.isi.edu>
On Allegro, type

 :zoom

to the debugger prompt.  Try typing :help to see what your options are.
I think you can also set things up to get an automatic zoom on entry
into the debugger.

For more details, hunt down the Allegro manuals.
-- 
Thomas A. Russ,  USC/Information Sciences Institute          ยทยทยท@isi.edu
comp.lang.lisp / 1997 / jul