
158 Configuration and Command Line Tools
fdb debugger
This section describes changes to the fdb debugger. For more information on using fds, see
Chapter 12, “Using the Command-Line Debugger,” in Building and Deploying Flex 2
Applications.
SWD files
The fdb debugger no longer uses SWD files. Instead, Flex generates debuggable SWF files by
using the
debug option with the mxmlc and compc command line compilers. There is no
longer a framework_debug.swc file. All the debug logic is built into the framework.swc.
Breakpoints
This section describes changes to breakpoints for Flex 2.
Player lock out
When you encounter a breakpoint with the fdb debugger, Flash Player locks out user
interaction. You cannot click on anything playing or access its menu options; you also cannot
close Flash Player and it does not redraw its display.
The reason for this behavior is to make breakpoints more predictable. For example, when you
are locked out of Flash Player, no other messages such as focus-change messages or user
interactions can change the results of the debugging session.
Deferred breakpoints
The fdb utility now supports deferred breakpoints. What this means is that if you try to set a
breakpoint, and the breakpoint location that you specified seems to indicate a filename or
function name that is not yet loaded into the Flash player, the fdb no longer reports an error;
instead, it remembers the breakpoint. If Flash Player eventually loads a movie that has code
from the source file that was specified in the earlier break command, fdb adds the breakpoint.
Commenti su questo manuale