[Ecls-list] finding point of errors

[Dean O'Connor]

Hopefully this is not too silly a question ... about fault 
finding/debugging ...

If I load a lisp script into ECL and there is some coding/syntax mistake 
and ECL spits an error such as this:

"Too few arguments supplied to a macro or a destructuring-bind form.
Broken at LOAD."

If I do a backtrace, its doesn't really give me many clues
eg.

"RAZOR-BASE>> :b
Backtrace: LOAD > eval > load > eval"

Are there any recommended quick ways (besides manual trail and error 
un/commenting) to pinpoint the area of the coding mistake ??

Trace ? or something ?

Cheers
Dean.