Problem with the FlashDevelop debugger

Question

As stated on the official website and in this thread ( FlashDevelop haxe (flash) debugger ), FlashDevelop comes with a debugger. But this does not always work for me.

I switched to FlashDevelop from CS, and first I used it with CS, like this: FlashCS3Workflow . Then I wanted to try this workflow: FlexAndFlashCS3Workflow and everything was right. But when my project grew, the debugger stopped waking up from time to time.

Even now I can set a braking point in some classes that are used at the beginning of the program, but if I set a breakpoint in some small or rarely used class, it will never be reached. But the code where the breakpoint is located is executed.

I tried with Debug -> Start Remote Session, but that did not help. Why don't breakpoints hit? I think I missed somenthing in the workflow or in setting up my project, but what?

The example above is for CS3, and I am using CS5, is this a problem? I also downloaded the Adobe Flash Player debugger and installed it, but that didn't help. Any ideas?

Answer 1

I also had a problem.

This is very annoying - the workaround sent by DoomGoober doesn't work for me either.

So far my findings are as follows:

A This happens if some of the sources are located in folders that are actually symbolic links - if you forgot to update the project view after moving or renaming the file.

B The first time I really listened to me, I phased out using all unexplored class references (e.g. var obj: * = ...) and replaced them with object type links (e.g. var obj: Object = ...) . (because I noticed earlier that some other secret errors occurred when using the Vector. <*> types in .swc - and I phased them first). That helped.

C However, later the problem returned. Reproducible, so far I can "fix" the problem when it occurs as follows: I know that it is difficult to believe - if I had not tested it myself, I could hardly believe it:

• I copied the entire project tree tree (including sources, etc.) to a USB drive (E: drive. Sources were originally on my drive D: hard drive).
• From this drive, E: I opened the project and built it there (age is required, but normal).
• Then the debugger worked fine.
• Close FlashDevelop.
• Copy the folder tree from drive E: to drive D :.
• The debugger is still working fine. - the problem is "fixed" !?

Note. I tried the same trick by copying it to another hard drive (my F: drive), but it doesn’t work?!?

This is vague and secret, but better than not entering half the classes. Holding his fingers, he will continue to work.

Answer 2

I had a problem with FlashDevelop that didn't reach the breakpoint at all. I installed the trial version of Flash, and then set the default program for SWF files to the Flash Debugger. This was in adobe/(adobe flash)/players/debug/FlashPlayerDebugger.exe .

I don’t know if this will help you or not with your problem, because I could not reach the milestones at all, but maybe it will help someone.

EDIT: I also found that if you install FlexSDK, it comes with FlashPlayerDebugger.exe which is used when debugging in FlashDevelop.

Answer 3

The workaround is to set a breakpoint in the constructor of your main class. FlashDevelop will hit this breakpoint, and magically all other breakpoints will start working.

Answer 4

It seems to work sometimes:

Create and debug a project on FlashPro CS5.5 once.

Or:

Imagine a compiler error (for example, a random hit on the keyboard) in a file where the breakpoint does not work. Let FD build and suffocate. Delete the entered error. Let FD build again.

This can solve problems for the FlashDevelop debugger.