Specifications

251ADOBE FLEX 3

Building and Deploying Adobe Flex 3 Applications

Using the command-line debugger commands

The fdb command-line debugger includes commands that you use to debug and navigate your Flex application.

Running the debugger

The fdb debugger provides several commands for stepping through the debugged application’s files. The following

table summarizes those commands:

When you start a session, fdb stops execution before Flex renders the application on the screen. Use the continue

command to get to the application’s starting screen.

The following example shows a sample application after it starts:

(fdb) continue

[trace] ComboBase: y = undefined text_mc.bl = undefined

Command Description

continue

Continues running the application.

file [file]

Specifies an application to be debugged, without starting it. This command does not cause the application to

start; use the

run command without an argument to start debugging the application.

finish

Continues until the function exits.

next [N]

Continues to the next source line in the application. The optional argument N means do this N times or until the

program stops for some other reason.

quit

Exits from the debug session.

run [file]

Starts a debugging session by running the specified file. To run the application that the file command previously

specified, execute the

run command without any options.

The run command starts the application in a browser or stand-alone Flash Player.

step [N]

Steps into the application. The optional argument N means do this N times or until the program stops for some

other reason.

These commands are nonblocking, which means that when they return, the client has at least begun the oper-

ation, but it has not necessarily finished it.