Yeah, you are losing the actual source of the error because of the catch block.
If you use fdb, you should be able to see where the real error is. Probably
just a brain-oh where it is looking for a property on a sealed object.
In general, the Debugger tends to bomb if you try to have it inspect itself. I
suppose it should work better, but it's pretty difficult, since it is trying to
iterate over itself and mutating itself to keep track of where it is at the
same time.
On 2010-10-28, at 14:27, Henry Minsky wrote:
> I'm working on fixing the "logdebug" feature for swf10, but came across an
> error when I tried to inspect the Debug
> object itself in swf10. The pretty printer gave an error referencing the
> 'description' property on String , not sure
> which method is trying to do this..
>
> lzx> Debug
> #Debug
> lzx> Debug.inspect(#Debug)
> ERROR @debugger/LzDebug.lzs≈1189: ReferenceError: Error #1069: Property
> description not found on String and there is no default value.
> null {
> atFreshLine: true
> atPrompt: false
>
> --
> Henry Minsky
> Software Architect
> [email protected]
