Oops.
I think that now that backtracing "works", debug always turns on catch-
errors.
I guess the way to get rid of the wrapper is to use a non-debug build.
The firebug debugger has gotten smart enough that it has a "Break On
All Errors" option, so you can debug your try/catch's. Does fdb maybe
have something like that?
On 2009-10-23, at 23:41, Henry Minsky wrote:
I'm trying to build a swf10 debug LFC with catcherrors disabled, so
I can
use the native flex fdb tool to step through and
catch errors.
But the LFC seems to be getting built with try-catch around every
method.
I'm doing
./buildlfcdebug --runtime=swf10
And it wraps a try-catch around each method, with a catch that looks
like
/* -*- file: -*- */
catch ($lzsc$e) {
if ($lzsc$e is Error && $lzsc$e !== lz["$lzsc$thrownError"]) {
$lzsc$runtime.$reportException("kernel/swf9/LzMouseKernel.as", 255,
$lzsc$e)
} else {
throw $lzsc$e
}};
Is there a way to get it to omit the whole try-catch wrapper entirely?
--
Henry Minsky
Software Architect
hmin...@laszlosystems.com
