1. Idiomatic lisp tends to consist of collections of very
short programs.  Therefore the name of the function is usually
a good way of localizing errors.  This information is available
using the top-level :zoom command.

2. Once you know the program name, you can trace it.  This offen
gives me what I need.  Sometimes it is useful to make sure that
the function you are tracing is not compiled. That way the :zoom
tells you even more details, like where in a COND the error
occurs.

3. There are many many other debug tools, but you are right that
a mapping between lines and errors is not what is usually available
because format info of this nature is not read into the running lisp.



Fabrizio Morbini wrote:

>Hi all, is it possible to have line informations of the errors? For
>debugging purpose is usefull know what line generates the error (I think
>that the line number is not possible because there is no mapping between
>the file and the functions, but at least print the expression that
>generate the error should be possible).
>
>Actually, to debug a program I use the classic "print" method...
>
>Thank you and Best Regards.
>
>Fabrizio.
>
>  
>