Wrong confirmation ID

Email
Favorite
Favorited ×
Download
Embed
Private Content
Copy and paste this code into your blog or website Copy Customize… Close
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.

Tweet

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Flex Debugging Tips and Tricks

by Saurabh Narula on Dec 02, 2009

1,978 views

Presentation at Adobe Developer Summit 2009 India at Chennai and Hyderabad.

Presentation at Adobe Developer Summit 2009 India at Chennai and Hyderabad.

Accessibility

View text version

Categories

Tags

ria hyderabad tips debugging tricks adobedevelopersummit india chennai flex4 flex adobe technology summit developer 2009 flex tips

Upload Details

Uploaded via SlideShare as Microsoft PowerPoint

Usage Rights

File a copyright complaint

4 Embeds 458

http://blog.saurabhnarula.com	321
http://saurabhnarula.com	127
http://www.slideshare.net	9
http://translate.googleusercontent.com	1

Statistics

Favorites: 1
Downloads: 40
Comments: 0
Embed Views: 458
Views on SlideShare: 1,520
Total Views: 1,978

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.

1 Favorite

Arulmurugan Thiagarajan , Software Programmer, Software Engineer, Web application Programmer at www.calsoftgroup.com Tags flex tips 2 years ago

Flex Debugging Tips and Tricks — Presentation Transcript

Flex Debugging Tips and Tricks Saurabh Narula http://blog.saurabhnarula.com/ http://twitter.com/saurabhnarula
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