Flex Builder 3 debugging trace output - apache-flex

I have installed Flex Builder 3 and Flash Player 10 on my machine.
I don't know where the trace output goes because I just don't see it (I tried debug and output windows).
Also the breakpoints don't hit.

Salut Omule :)
If you press the Debug Icon(the bug thingy) or go to Run > Debug you should go to the Debugging perspective.
If might be handy to install the Flash Tracer plugin for Firefox to see your traces from the browser.
First you need to make sure you have the Debug version of Flash Player 10. You can do that by checking is Debugging is true using this test.

You can view traced messages in the console (Menubar - Window - Console).
But since you said that breakpoints are not hit, I guess the problem is somewhere else. Make sure that you are debugging instead of running the app (select Debug from the Run menu or just hit F11 while at the corresponding mxml file).
If that doesn't help, and if you are on Firefox, try uninstalling the last addon that you installed. Some addons (including older versions of google toolbar and adblock plus) have known to block swfs from connecting to the flex builder's debugger.

Related

Samples don't work in Google NaCl rev 18

I'm trying to use the latest Google NaCl SDK. Following the instructions at https://developers.google.com/native-client/pepper18/devguide/tutorial
I downloaded the naclsdk tool from their site, ran update, and got a pepper_18 folder.
I set NACL_SDK_ROOT to the pepper_18 folder, went in to 'examples' and ran make. Everything seemed to compile just fine.
I started Chrome, looked in about: flags and about: plugins, and verified that NaCl is enabled. I installed the SDK Examples app (from: https://developers.google.com/native-client/pepper18/sdk/examples) and that works just fine.
Then I tried to run my locally built and hosted examples, going to http://localhost: 5301. The HTML loads fine but the NaCl content does not load. In the hello world examples, it says "Status: LOADING..." forever.
I double checked the HTTP server logs and I don't see any errors there. Is there another place I should be looking for logged errors?
Check for version mismatch
In Chrome navigate to about:version and check that the major version of Chrome is at least that of the Pepper version you used to build your examples.
Check the JavaScript console in Chrome for any errors
You can find it by clicking the wrench icon in the upper right-hand corner in Chrome and selecting Tools -> JavaScript Console.
Inspect the NaCl module for further information
In the JavaScript console, you can also inspect the embed element of the NaCl module. E.g., if the embed tag has id="nacl_module" you can inspect it by typing
theModule = document.getElementById('nacl_module');
theModule.lastError;
Check Chrome's output to stdout/stderr
On Mac or Linux start Chrome from the terminal and look at the output on the console. E.g., on the Mac, you'd typically go
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-nacl
On Windows, Chrome does not write to the terminal if started from a command prompt. For this reason you need to redirect stdout/stderr from Chrome by setting the environment variables NACLLOG, NACL_EXE_STDOUT, and NACL_EXE_STDERR. Point them to different files, e.g.,
NACLLOG = c:\my_project\nacl.log
NACL_EXE_STDOUT = c:\my_project\nacl_stdout.log
NACL_EXE_STDERR = c:\my_project\nacl_stderr.log
Then (re-)start Chrome (making sure these environment variables are in effect).
Connect a debugger
Instructions on using the debugging support (currently only 64-bit Windows and 64-bit Linux) are available at https://developers.google.com/native-client/pepper18/beta-docs/debugging.
Restarting Chrome means closing all windows
When developing for Native Client one often restarts Chrome. It is important to close all Chrome windows; otherwise it hasn't actually restarted.
I muddled through a few issues which I will document in case they help others:
Neglected to 'make' the examples (got a clue to make them from the asker's description).
Chrome would not let me run non-store chrome apps. Went to chrome://flags and enabled Native Client and Native Client GDB-based debugging.
The JavaScript console said the demo's nmf file under .../debug/ was missing. I changed the make config to build Debug instead of Release based on this.
Chrome console complained NativeClient: NaCl module load failed: ServiceRuntime: failed to start; NaCl's GDB debug stub requires --no-sandbox flag on Windows. See crbug…. Tried running Chrome from cmd with --no-sandbox. This results in an alert You are using an unsupported command-line flag: --nosandbox. Stability and security will suffer. The aforementioned error went away, but the examples still would not run - no UI.
Went back to chrome://flags and disabled Native Client GDB-based debugging.
Then most of the examples worked. The Google Drive demo complains Error: must be run as a packged app.
have you confirmed that you've run httpd.py from the examples folder? This script creates the localhost:5103 server that the apps can be ran from.
Also, what OS are you using?
~Main

Flash Builder 4 - Flash Player failed to connect to debugger

I just finished my installation of Adobe Flash Builder 4. I've definitely installed the most recent flash player from Adobe's website onto my computer. Also, in the run configurations of flash builder 4, I changed the source path from the .html file to the .swf file that is generated. I don't need to test it in a web browser, I just want to run the swf in flash player.
I only have 1 .as file in my actionscript project and there is no code written in it other than the package, class and main function statements. When I run the .html file, it runs fine, and debugs fine. However, when I switch the source path to the .swf file, it runs fine but doesn't debug!
When I debug it, the progress gets stuck at 57% and it says "Waiting for Adobe Flash Player to connect to debugger..." in the "Progress" tab. After a few minutes a window pops up that says:
"Failed to connect. The session has timed out. Ensure that you have run the application with debugging on and that I have the debugger version of flash player."
What can I do to fix this? I am on an intel Mac running OS 10.6.5.
Thanks
You say you installed the most recent Flash Player, but you don't say if you by that mean the debug player. The "Flash Player 10.1 Plugin content debugger" and "Flash Player 10.1 Projector content debugger" can be downloader at http://www.adobe.com/support/flashplayer/downloads.html
This might solve your problem
http://blog.air4android.com/?p=59
HTH
I had exactly that symptom.
I cleaned all related projects, removed bin-debug and bin-release, cleaned the cache, reinstalled the debug version of the player. It didn't help. I was about to reinstall FlashBuilder.
Then I displayed the javascript console. I saw there is a syntax error in my index.template. As a result, the application was never started, so the screen remained blank and the debugger failed to connect.
I fixed the silly error and it worked again! Basically, that message tells you the application failed to start.
Make sure you're not using Chrome. At time of writing Flash Player debugger does not work in Chrome.
I had this problem and simply switched the web browser to Safari in Flash Builder preferences.
what worked for me finally was copying the swfobject.js to the bin-debug folder. I don't know why it wasn't there, but that fixed the problem.
you do, of course, have to run a flash debugger version in your browser.

Waiting for flash player to connect to debugger

Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?
I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance
Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.
This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4
Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.
Changing the browser from default (chrome) to IE worked for me
Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.
Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.
To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.

Flex Builder 3 not debugging

Allope,
I've recently bough Flex Builder 3 and I am completely dissatisfied with its reluctance to debug. It manages to debug a few times, but after that, it just doesn't want to "connect to the debugger".
Help?
There is no easy fix for this. You now have to join the rest of us waiting for Adobe to update Flex Builder with a fix they say they have.
You can find the long sad story here: http://bugs.adobe.com/jira/browse/FB-16153:
Basically, this is an issue that has been around for months. Adobe says it has a fix - however - they've not released that fix yet. Adobe reports it's a threading issue...
For the rest of us (waiting for this) - if you need to move forward you can:
A) Live with the problem (painful)
1) Note that in the bug text there are several attempts to work around this - sometimes people find ways to soften the issue - but no one reports a full fix
2) Note that people trying the LocalHost fix - sometimes report a gain in productivity - but in most cases they do not.
B) Switch SDKs from 3.2 (or 3.3) to 3.1 ---- No one knows why - but it fixes the problem (you can then include the SWFs you need for 3.2 directly
C) Develop on Mac [Not a smart ass answer - honestly - for whatever reason this bug is not on Flex Builder for the Mac]
Join the bug discussion - on Adobe's site - it's still active as people are still waiting for the fix.
Make sure you have the required Flash Debug Player.
http://www.adobe.com/support/flashplayer/downloads.html
If that doesn't help, you might have to re-install Flex Builder.
Are you running it on windows vista? It may be this issue:
http://blogs.msdn.com/expression/archive/2009/03/16/page-cannot-be-found-issue-when-previewing-via-expression-blend.aspx
The page is about silverlight, but I ran into the same issue a while back with the flex debugger, and had to add the following to my host file (which windows defender removed):
127.0.0.1 localhost
This is expanded more upon here:
http://circstar.com/FlashLabUnderground/?p=64
I've had similar problems but every-time it refuses to connect to the debugger i have justed downloaded and reinstalled the flash debugger and it works fine. It's a pain but until adobe do anything what can we do?
Have you the tried FlashDeveloper ide? you can build flex project with it and it quite frankly alot better than flex builder for code writing (not ui work).
Hope this helps
Jon
I'm not sure if you have the same symptoms, but I came across a similar problem on one of our development machines after installing Flex Builder 3. When trying to run our app in debug mode, flex builder took a long time to launch the app and eventually timed out, displaying some message about not being able to connect to the debugger.
I found this solution which worked a treat. While Flex Builder is trying to launch the app:
Go to the browser page containing your app/swf, right-click on the swf to bring up the flash context menu.
Select Debugger
Select Other Machine
Enter 127.0.0.1 in the text field
Click Connect and hopefully it works.
NB: If Flex Builder tried to launch the app in Firefox, the page never appeared. It was only when it launched in Safari that I was able to access the browser page and the flash context menu.

Severe Flex issues

I seem to be having difficulties getting the trace function to output anything to the console in either Eclipse with the Flex Plug-in, Flex Builder, or even FlexBeans (the Netbeans plug-in for Flex). I have removed and then reinstalled the Flash player 10 debugger version for both Firefox and IE, rebooting after uninstalling them and then after re-installing them. I have removed all old versions of Java and updated to the most recent version.
mm.cfg is configured correctly to allow the trace actions to appear in flashlog.txt
I tried removing the Flex Plug-in for eclipse to re-install, and now that I re-installed, I cannot create new Flex projects. I would rather not uninstall Flex Builder for fear that it will also behave strangely.
ANY ideas would be useful. Ideally, I need the plug-in to work, but any way I could get tracing to output to the console (in ANY IDE) would be better than what I have now.
I'm not sure what you mean by "Flash debugger for both Firefox and IE"; are you referring the debugger versions of the Flash Player available here?
http://www.adobe.com/support/flashplayer/downloads.html
If not, you definitely need those installed in order to be able to write trace() output to the IDE console.
I'm almost positive that this is not the issue, but it has confused me on a couple of occasions.
The Debug Application (as opposed to Run Application) keyboard command is different on Mac and PC. I use both and have gotten them mixed up, which results in my Running when I think I am Debugging, which of course leads to know trace outputs in the console.
Most likely not it, but doesn't hurt to mention it (I hope) :)
-- Evan
How are you testing the debugger? Have you tried going somewhere like with lots of ads that generally still have their traces in? Or are you just testing it with your own swfs? Have you installed the projector debug version? How is eclipse / flex configured to launch test swfs? Is it in the browser, or in the stand alone player? Do you have any weird mxmlc settings?
I assume you've followed all these instructions?
http://kb2.adobe.com/cps/193/tn_19323.html
This is actually a combination of issues. The minor issue was that one application was interfering with Flex Builder Plug-in. The major issue had to do with a setting which had gotten changed on the Flash debugger.
If you right-click the running SWF and then click Debugger, you can (essencially) tell the VM where to listen for trace actions. This had been set to another machine on the network, and not my local machine. As soon as that was switched, everything restored itself.

Resources