Flex Debugging Tips and Tricks
•Download as PPT, PDF•
1 like•637 views
This document provides tips for debugging Flex applications including basic debugging in Flash Builder, new debugging features like watchpoints and conditional breakpoints, using the DeMonster Debugger tool for its tree structure and live editing capabilities, and testing with the Alcon Debugger.
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Flex Debugging Tips and Tricks
- 1. Flex Debugging Tips and Tricks Saurabh Narula http://blog.saurabhnarula.com/ http://twitter.com/saurabhnarula
- 2. 1. Basic Debugging in Flash Builder 2. Debugging Perspective: new features Watchpoints Conditional Breakpoints Run to line 3. DeMonster Debugger Tree Structure Live Editing Detailed Traces Method Testing 4. Alcon Debugger
Editor's Notes
- Watchpoints - there was no way to select a specific variable instance for monitoring during your debug session Conditional BreakPoints - Debugging with breakpoints can quickly become cumbersome. Consider a situation in which you needed to troubleshoot an issue within a for loop. You may need to suspend the application only once during the debug session to verify your logic, but you’ll hit the breakpoint in the for loop each time through. You’ll then have to take the additional step of removing the breakpoint to continue the debug session without stopping on each iteration of the loop. Using conditional breakpoints in Flash Builder 4 you can configure a breakpoint to trigger only after a certain number of loop iterations. For instance, you can halt the application on the third time a breakpoint is reached. You can also use a conditional breakpoint to suspend the application when a particular expression either changes or evaluates to true Run to line - In the past, if you hit a breakpoint and wanted to know what would happen ten lines down through code execution, you would need to step debug until you got to the line you wanted to investigate. Other options would be to set another breakpoint, or even create a trace statement. Although all these options are valid, they can be inconvenient. A better solution would be to use the run to line feature in Flash Builder 4 to quickly get to a line in the code below the breakpoint that the application had suspended on. In this walkthrough you will use run to line to get to the trace statement after the for each loop quickly. Monster Debugger – debug/ introspect your swf file, while its running.