From: Nonzero
Subject: Debugging with CLISP
Date: Tue, 30 Oct 2001 14:59:47 +0000
Message-ID: <2e3cbcd8.0110300659.6aeffa07@posting.google.com>

Hello all.

This is great!  I now have genetic programs from Koza's book running
on my computer.  This is fun.

One question though.

Every once in a while CLISP will give me an error message after the
program has been running.  Usually it's somthing like:

*** argument to = must be 0 nil

Is there anyway I can find out *which* = statement it is having a
problem with?? (like getting a line number or something)

Thanks in advance

Nonzero314

From: Geoff Summerhayes
Subject: Re: Debugging with CLISP
Date: Tue, 30 Oct 2001 16:06:07 +0000
Message-ID: <tttk1fi3r6i157@corp.supernews.com>

"Nonzero" <··········@hotmail.com> wrote in message
·································@posting.google.com...
> Hello all.
>
> This is great!  I now have genetic programs from Koza's book running
> on my computer.  This is fun.
>
> One question though.
>
> Every once in a while CLISP will give me an error message after the
> program has been running.  Usually it's somthing like:
>
> *** argument to = must be 0 nil
>
> Is there anyway I can find out *which* = statement it is having a
> problem with?? (like getting a line number or something)
>

Try (SYSTEM::DEBUG-BACKTRACE)

Geoff