Will try to merge and check that doesn't break anything in FB too.
Thanks,
Frédéric THOMAS
> Date: Wed, 15 Jan 2014 15:53:58 +0400
> From: alexander.doros...@jetbrains.com
> To: dev@flex.apache.org
> Subject: Re: FDB vs FB debugging ?
>
> > Btw, while you here, can you tell me what C:\Program Files
> > (x86)\JetBrains\IntelliJ IDEA
> > 13.0\plugins\flex\lib\idea-fdb-4.5.0.20967-fix.jar is for?
> Source code for my patch can be found in [IntelliJ IDEA
> Installation]/plugins/flex/lib/idea-fdb-4.5.0.20967-fix_src.zip.
> It solves some issues:
>
> 1. escapes CRLF and some other special chars in fdb output that makes it
> easier to work with it at IDE side
>
> 2. adds file id to the stack info printed by fdb (line 1182 in original
> file == line 1178 in my patch)
>
> boolean valid = appendFrameInfo(sb, frame, i, showThis, false);*=>* boolean
> valid = appendFrameInfo(sb, frame, i, showThis, true);
>
> 3. prints full stack if Flash Player detects not handled exception
> (original fdb prints only error message).
>
> See void dumpFaultLine(FaultEvent e){...}
>
> 4. The most important fix is inside findAndEnableBreak(...) method
> implementation and it solves the following issues:
>
> Impossible to set breakpoint in MXML files that contains item renderer
> (http://youtrack.jetbrains.com/issue/IDEA-57546)
>
> Breakpoints in ActionScript files do not work when debugging app using ANE
> (http://youtrack.jetbrains.com/issue/IDEA-94128)
>
>
> I think all fixes except the first one can be added to Apache repo. All
> of them are in a DebugCLI.java file. The most important is the 4th case
> with breakpoints not working without a fix.
>
> Alexander
