FlexDbg

This is a debugger plugin. It is based on a fork of fdbplugin which has been rewritten to interface directly with class libraries containing the debugger classes from the Adobe (tm) OpenSource Flex SDK (tm) ported from Java to C#.

The following functionality is now working:

• Target Launch
• Breakpoints
• Stack Frames
• Locals Window that displays Local Variables, Arguments and this
• Step, Next, and Finish
• ToolStrip with buttons for Continue, Pause, Stop, Step, Next, Finish
• AIR Support (Not tested yet)
• Breakpoint toggle by clicking next to line
• Values changed since the last breakpoint are displayed in red
• Setting Variables
• Reset display to current file and current line button / menu
• Fix DataToolTip Resizing
• Source path list so that you can step into the framework if you have the source on the machine
• Conditional Breakpoints
• Continue execution until the current line

In other words, all of the functionality of the existing fdbplugin plus much, much more.

Within the next couple of weeks I should have the following features available:

• Remote Debugging and Debugging standalone applications which use the embedded ActiveX control
• Watchpoints (break when a variable's value changes)
• Save / restore ToolBar location
• Expression Watch Window
• Other things I can't remember right now

If your favorite wishlist item isn't listed above now is the time to get your vote in!

Version 0.9.8 is now available!

Latest Changes

• Conditional Breakpoints
• Continue execution to current line
• Complete rewrite of the DataTip control, 3 controls reduced to 1 and standard window visuals when resizing manually
• Fixed wheel mouse scrolling in the tree control.

Project Link: http://gforge.opensource-sw.net/projects/flexdbg
(warning, latest version hosted in FlashDevelop SVN)

Version 0.9.8 is now available (Forked by Philippe from FD team and zobo from forum):
Download FlexDbd 0.9.8

This sounds great! This definitely a feature that has been high on a number of wish lists.

Looking forward to when we can play with an alpha or beta release!

Sounds totally cool. I've looked into porting Fdb to C# but I thought it might be a problem to follow future versions of the SDK.

Also did you check the code license? Does it allow for porting/hosting the code?

PS: don't forget to try with code heavy (ie. 3D stuff) and multi-frames SWFs (as in "AS3 project with preloader" template).

That's what I have been waiting for! If you can include conditional watch or break on condition feature, that would make it even sweeter. Well, I would love to chip in my help too as I am a C# programmer too.

Philippe,

The licensing is a little confusing since they threw in the old pre-opensouce license in the directory with the other licensing materials. But the intent seems clear. They've split the SDK into two parts, the opensource components and the opensource addons. The opensource components are licensed under the Mozilla Public License which allows all the usual opensource things such as modifying, porting and redistributing. The debugger is included as part of the opensource components.

As far as maintaining compatibility with future versions, that is always a challenge. I created a branch in subversion of the 3.3.0 source I started with. As long as future versions remain opensource it should be reasonably easy to identify the changes and incorporate them into the ported version.

Can't wait to see this!

Also noticed this on the Open Souce FAQ

If I use the open source version of the Flex SDK in my product can I call it Flex?
No. Adobe Flex is a trademark owned by Adobe Systems Incorporated for use only with commercial applications distributed by Adobe.

Unfortunately that FAQ is way out of date, written at the time of the announcement but before the OpenSource version of the SDK was available.

I think the plugin being called FlexDbg is okay since it isn't claiming to be Adobe Flex. As far as the ported Flex SDK components are concerned I think they are okay too as long as they don't claim to be the Adobe Flex SDK. I think it is okay to say that they are derived from the opensource Flex SDK, in fact it seems to be required by the license.

I'll have to be careful to make sure I put the appropriate marks in any documentation referring to Flex.

Well I finally managed to get the first alpha version of the new debugger released!

I wasted four days trying to track down a bug with breakpoints not firing sometimes if you spend a lot of time browsing the variables in the Locals window. It turns out to be a bug in the Flash Player. The same problem occurs when using Adobe's Flex Builder 3.

There is still a bunch of polishing to do and a few more essential features left to implement. But I think it works better than what is available now and I would like to get feedback from users while I continue to work on it.

Hi,

I'm been trying to get this plugin to work on my flashDevelop installation but it keeps crashing when loading. I get three windows poping up (Locals, Breakpoints, Stack) and then crashes. I currently have version 3 Beta9 installed. I copied all the files into the plugin folder. Is there anything I'm doing wrong?

Hi, have been waiting for this for a while!
Great work!

I have it installed fine, and it runs up, however the application needs to be run from within a browser / web server. It cannot be run locally via flash player stand alone.

Is there any way at the moment to NOT debug with the standalone player?

Ideally, we need a way to launch the debugger and then it waits for the player to connect, and then we can boot up the relevant swf via the web browser.

is this currently possible?

cheers, m.

mumf83,

This plugin has been built and tested to run against the latest version 3.0.0 RC2.

mattb,

I just released a new version (0.9.2) that launches the standalone player if the Project Settings - Test Movie option is set to default or External Player. If it is set to Open Document then the specified URL is launched instead.

When I change the document class and try to compile (from debugger):
- debugger doesn't pick that change from the project (compiles the previous document class).
- after I close the flash player pop-up FlashDevelop process takes over 99% ov CPU and won't release them unless forced to shut down...
.NET Framework 3.5 WinXP SP3.

Tried the plugin (with FD SVN build) and I'd say it's a good start.
Like, stepping and live data inspection is actually fast!

Lot's of bugs thought
- debugger doesn't "see" the Flash was started if you don't set a breakpoint in the main class' constructor,
- gets crazy if you close the player directly (instead of debugger's Stop button): FD quickly freezes,
- debug a SWF, press Pause, then hover to have the tip appear: brings a null reference exception in FlexDbg
- seems to be some unsafe threading going: repeatedly pause/step/continue a SWF (no need to hurry) and you'll get threading violation exceptions or screwed Scintilla text (cleaned after another step),
- live tip doesn't resize properly when you expand/contract values.

Apparently you are not building the SWF, right?

PS: is it possible to start without debugging? (ie. let FD default basic debugging)

Continue the great work!

wvxvw,

Which version of the debugger plugin are you running?

The debugger isn't involved in compiling your project. If the compiler isn't compiling the latest version of the source you need to post your question in another thread in the appropriate forum.

Having said that, if you rebuild your swf file then you need to stop the debugger and relaunch your application to test those changes.

I'll take a look at the CPU usage issue later today.

I´m having the same issues as wvxvw described above.

But I salute you for your great work so far!!!

.NET Framework 3.5, Vista SP1, FlashDevelop 3.0.0 RC2

/Bjarne