You should be able to inspect the recursive error (the `#...`), which hopefully
points to where the internal error is.
Maybe I can move the try/catch "in" to have it not lose _everything_ when it
trips over an error. I'll look at that.
IM me if you want.
On 2010-11-30, at 11:58, Henry Minsky wrote:
> So, where would I start to look for what's causing this error in printing
> out a backtrace
>
>
> lzx> Debug.inspect(«LzError(128)| @../../foundation/restricted/D…»)
> «LzError(128)#3| @../../foundation/restricted/DefinitionLoader.lzx#137:
> TypeError: Error #1010: A term is undefined and has no …» {
> Error: ReferenceError: Error #… computing inspectInternal}
>
>
>
>
>
> --
> Henry Minsky
> Software Architect
> [email protected]
