A–C
D–H
I–Z
Developer services
Project centers
Community resources
- Adobe Cookbooks (share code)
- CSS Advisor (browser bug fixes)
- Exchanges (share components)
- Adobe Labs
- Adobe Open Source
- Forums
- RSS feeds
- Bug base
- User groups
- Adobe Community Experts (ACE)
- Developer events
Integration
Product documentation
Downloads
Samples
Training and books
- Online training
- Classroom training
- Certification
- Adobe Developer Library
- Adobe Press
- Safari Books Online
Newsletters
Blogs
Archives
ADC program
Additional resources
Table of Contents
- Introduction
- Managing Breakpoints
- Starting a Debug Session
- The Debug Interface
- The No Breakpoints Dialog Box
Debugging Flex Applications with Flex Builder
Starting a Debug Session
Once you have set your desired breakpoints, it's time to start debugging the application. The easiest way to start a debug session is to choose Debug view from the toolbar. By selecting this view, Flex Builder uploads the test file with any dependent files and starts a debug session with the Flash Player. Once the Flash Player debug session starts, the player contacts Flex Builder and starts to play your application. You can quickly access the Debug view by pressing Alt + F6.
Figure 3. The Debug view
If you prefer testing your applications in an external browser, you can still take advantage of Flex Builder’s debugging tools. To start an external debug session, select Debug in Browser from the toolbar, use the keyboard shortcut Alt+F12, or File > Debug. You can also start a debug session from the Run Debug button in Network Monitor and Output panels.
Figure 4. Starting a debug session in an external browser
Using an external browser session for debugging is similar to using the Debug view. Flex Builder uploads the files and creates a debug connection with the external browser. When it encounters a breakpoint in an external browser session, Flex Builder regains focus and displays the code, just like in the Debug view.
