FB4.6 debugger issue

Hi all,
After update the new version of flash and installing the debugger, i am getting this error:
C:\Windows\System32\Macromed\Flash\NPSWF64_11_1_102.dll
Flash Builder cannot locate the required debugger version of Adobe Flash Player. You might need to install the debugger version of the Flash Player or reinstall Flash Builder.
Do you want to try to debug with the current version?
If i click YES, it pass... but sometimes the debugger doesn't work
Anyone can help with this issue?
Thanks!

This is a known bug for Flash Builder 4.5 and 4.6.
It will be fixed in next version of Flash Builder.
The workaround for Flash Builder 4.5 & 4.6 is to download both 32-bit & 64-bit debug player.

Similar Messages

10.9.2 Update Issue (VPN) - Eclipse Perl debugger issues while connected to VPN

This post was initially added to this discussion: 10.9.2 Mavericks update issues
I have yet another issue related to 10.9.2 update - Eclipse Perl debugger issues while connected to VPN...
One of the big changes introduced by 10.9.2 update - are VPN changes (security fixes). Unfortunately, whatever these changes are - they "broke" Eclipse (OpenSource IDE) debugger. I am not sure if *all* programming languages (Eclipse plugins) are affected by this, but I know for sure that 'Epic' (Perl plugin) debugger *stopped working* while system is connected through VPN.
Here is the error that gets “popped-up” in the Eclipse:
Timed out while waiting for Perl debugger connection
… and here is exact exception stack that gets printed:
Unable to connect to remote host: 130.10.210.74:5000
Compilation failed in require.
at /Users/valeriy/workspace/ROBO-PROD-RA-685/src/lib/test/Val_test.pm line 0.
main::BEGIN() called at /Users/valeriy/workspace/.metadata/.plugins/org.epic.debug/perl5db.pl line 0
eval {...} called at /Users/valeriy/workspace/.metadata/.plugins/org.epic.debug/perl5db.pl line 0
BEGIN failed--compilation aborted.
at /Users/valeriy/workspace/ROBO-PROD-RA-685/src/lib/test/Val_test.pm line 0.
Can't use an undefined value as a symbol reference at /Users/valeriy/workspace/.metadata/.plugins/org.epic.debug/perl5db.pl line 7596.
END failed--call queue aborted.
at /Users/valeriy/workspace/ROBO-PROD-RA-685/src/lib/test/Val_test.pm line 0.
(of course IP address changes dynamically for each VPN connection session)…
I was able to prove that this issue is related to 10.9.2 update:
Issue *does not* exist under 10.9.1 (I had to revert back to 10.9.1 to get it working again)
No updates were performed around the same time 10.9.2 update occurred (I verified that using Software Update log)
No configuration changes were introduced around the same time
Reverting back to 10.9.1 using Time Machine (thanks god I had backup !!!) fixed the issue
Steps to reproduce this issue:
In Eclipse, try to use 'Epic' (Perl plugin) to debug any perl script while *not* connected through VPNEpic debugger works
Connect to VPN
Start Epic debugger to debug same script
Debugger *does not* start, and "Timed out while waiting for Perl debugger connection" error pop-up comes up after some time. At the same time, exception stack (listed above) is printed in Eclipse's console
I am programmer/software developer, I work remotely (telecommute) and thus have to rely on use of VPN to connect to company's intranet. Perl - is primary language used by my team, and we use Eclipse IDE with Epic plugin - heavily. Use of Epic's debugger - is a *very large* aspect of my work, I cannot work without it. So in essense, 10.9.2 has *entirely* disrupted my ability to work! It took me almost a week to get back to normal work environment, and I cannot afford to let it happen again... I need Apple's development team resolve this VPN related issue, as soon as possible! Because of this issue, I am *stuck* with 10.9.1 and can not upgrade my laptop to any other versions. In fact, I had to disable system updates - just so I do not run into this issue again... I contacted Apple's Tech Support on 02/28 with this issue (Ref: 582428110), asking to raise trouble ticket. Since then, I tried to follow-up on that issue, but do not get any information. Please advise on the status:
is there a trouble ticket to track this issue?
is there any progress?
what's the ETA for an update that fixes this problem?
- Val
Message was edited by: vpogrebi

Am I the only one experiencing this issue ???

Possible debugger issue.

I am trying to debug a third party package which fails in the debugger but runs OK.
There are two issues.
1 It includes the following code in the package body (ie as package initialisation).
    gv_audit_dir := TRIM(pk_dbgen.GET_SYSTEM_PARAMETER(pmi_systemparameter_in => pk_parms_global.gi_drive_path))
                 || TRIM(pk_dbgen.GET_SYSTEM_PARAMETER(pmi_systemparameter_in => 20));
    dbms_output.put_line('AUDIT_DIR='||gv_audit_dir);
    IF LENGTH(gv_audit_dir) < 4 THEN
      gv_audit_dir := NULL;
    END IF;When this code is stepped through in the debugger, the 'if LENGTH(gv_audit_dir) < 4' condition is always true, regardless of the actual content of the variable. If I step over it seems to execute OK.
2. The procedure I am calling fails with primary key violations if run in the debugger, but works if run normally. It is doing too much for me to pin down where the failure is at the moment, but I'll try to simplify and reproduce.
Has anyone seen this kind of behaviour in the debugger.
SQLDeveloper 1557
RDBMS 9.2.0.7

After two days of trying I somehow managed to revive my iPod. First, I re-partitioned for PC. Next, I reformatted for DOS and zeroed all data. Just for kicks I repeated the process for OSX extended. Finally, I ran Restore. It restored very quickly. I still wasn't convinced so I Restored several more times. This time when I updated my iTunes library to the iPod it transferred very quickly and without any apparent pauses.

FLASH Builder 4.5 Debugger Issues

Hey,
Recently the projects I've been working on have had additional compiler arguments added to it:
http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_21.html
(e.g. -define+=myval,true -define+=myvalx,false)
This works ok for the compiler but I'm noticing now sometimes my FLASH Builder will now trigger breakpoints in external libraries no matter what I do.
I've referenced the library directly from my application, removed any swc references internally, did a clean etc. This never happened before when I never had these conditional compiler arguments. Breakpoints also work fine within the context of the main application.
Has anyone experienced this before and know anyway to work around it?
(This doesn't ALWAYS happen, sometimes the very same library works fine, but other times it does not)
Thanks,
Sean

My two cents on this issue & how I resolved it.
I was getting a similar message which referenced a location in C:\Windows\System32\Macromed\Flash, and was looking for this version of the Flash Player: Flash64_10_3_162.ocx
What I tried that did NOT help:
Re-associating the SWF file type to open with a Flash Player debugger version downloaded from Adobe's site.
These three steps resolved the issue for me:
I had installed the 64-bit version of the Flash Player a few months ago, so I uninstalled that since it cannot be used by Flash Builder as a debugger. Back in FB 4.5.1, I got another message saying Flash was not installed at all.
I used Adobe's Flash uninstaller tool and then,
re-installed the latest debuggers for IE & Firefox.
I can now debug in IE or FF without any issues. FB finds the debug version of the Flash Player.
From what I saw when researching this, there seem to be many causes for this issue so I'll give Adobe some slack here. I will point out that the post from Adobe employee Anirudh Sasikumar, above, was not helpful in my case and was in fact misleading and not specific enough as to the location of the file he referenced. I searched for that file and found dozens of them on my machine, none in any location he mentioned. I wish he would have taken a little more time to give a complete path to this file. Maybe he did, but I could not find that path, or folders, on my machine. I work in a tightly-controlled network environment so perhaps these folders are ones I cannot see due to permissions issues, but it would've saved me time to get a complete path to start with.
For complete and full disclosure, here is my set-up; hopefully this will help others with a similar setup who are experiencing this nagging issue:
Windows 7 Enterprise 64-bit, Service Pack 1
Flash Builder 4.5.1.313231
Eclipse 3.6.1r361_v20100909xxxxxxx
Flash Debugger version (IE & FF): 10.3 r183

Flash Debugger issue

Hi,
I'm trying to use the Flash debugger but when I put breakpoints in nothing happens except I see the swf. I can't run through the code or see any variables?!
I'm coding in AS3 and I'm using CS4 professional on Windows XP professional platform.
Thanks in advance for any help.

I've installed flash again but the debug still doesn't work still.
I've managed to debugged my FLA on a colleagues machine without any problems so I know it's not the flash files!
Anybody got any ideas what I can try next?

Flash builder 4 and flash 10.1 standalone debugger issue on osx

If I use the standalone flash debugger version (Flash Player Debugger 10.1.52.14) with flash builder 4 on osx 10.6.3 then this happens:
I compile the project and the debugger opens. If I click the red stop button then it never closes the debugger. I have to close it manually. Doing that means I have to use clean alot more and often up to 3 renders open after that.
If I switch over to the standalone "Flash Player Debugger 10.0.42.34" then the red stop button works fine and I dont get duplicate players launching.
Anyone else experience this?
I don't use the web player versions.

10.1.53.64 is the latest standalone version. Could you please try with that version?
You'll get it here: http://www.adobe.com/support/flashplayer/downloads.html

Sql developer debugger issue

I am using oracle sqldeveloper 1.0.0.15.57. Previously we were able to set up a breakpoint and step through a stored procedure inside a package.
We made sure all the previliges are on and the debugging did really work.
But after some time (no changes to the Database or to the setup configuration on my laptop), we are not able to step through the stored procedure in a package.
This is the logs we get:
Connecting to the database UAT_Staging.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '10.3.18.51', '1346' )
Debugger accepted connection from database on port 1346.
Processing 56 classes that have already been prepared...
Finished processing prepared classes.
Process exited.
Disconnecting from the database UAT_Staging.
Debugger disconnected from database.
We do get all the log statements indicating that the SP is running, but the control doesn't stop at the breakpoint, preventing us from debugging.
Can someone help, as to why this is happening?
Thanks
karthik

I guess you've bumped onto the HUGE breakpoint-line-bug.
I guess it's since developer cuts the first line in two:
CREATE OR REPLACE
PACKAGE BODY XXX AS
the line numbers internally are 1 off.
If you want to break at line 101, place the breakpiont at 100...
DEV TEAM, how long before you can fix this one? It's an ugly, error prone, dev time consuming bug!
K.

Installing Flash Player Debugger Issue

In our organisation we are not allowed to install any software/package so easily. The thing is by default all the machine have flash player (version 11.4) and in one of the machine I want to install flash player debugger (11.0). But the system not allowing to install flash player debugger because, the flash player is already available in the system. Can you tell me how to install flash player debgger without uninstalling existing flash player. Is it possible to customize flash player debugger by removing flash player and keep only in debugger? thanks in advance. Srini

Hi mr.adrianp,
We are happy to help you and let you come out of the trouble that has been caused to you while using Adobe product.
Please refer the KB doc link mentioned below for the same:
Flash Player with Google Chrome
Hope this helps. Let me know if you need further assistance.
Regards,
Anubha

Flex debugger issue

When I run flex application it keeps showing popup window
saying
“Where is the debugger or host application
running?”
choose between : localhost or IP?
is anybody know how to avoid this?
Thanks!
Jamil

Can it be that your running the debug version of your
compiled flex appliaction (SWF file) ?
If I start the debug version outside Flexbuilder I got the
same question.
If I use the normal version no question is asked.
regards,
kcell

Debugger issues...

I've been trying to figure this out for a while now but I
just can't.... for some strange reason the debugger does not
display any arrays. Everything else works fine, but arrays don't.
They just don't show up in the list of variables at all as if they
didn't exist... did this ever happen to anyone?

I have an update that might help...
The arrays that are "invisible" in the debugger are those
that are created and instanciated in an as file. All of the other
variables from the as file are visible. If I make an array in the
fla flie, the debugger sees it.

Debugger issue - local variable table missing

I have compiled my sources using IBM's jikes compiler with the -g option (for debugging purposes). I am using Sun's JRE 1.2.2. and JPDA 1.0.
When I run the debugger using JPDA and try to set a watch for local variables I get an error saying that the local variable table is missing. And it asks me to compile the source with the debug option (which I've already done but with the jikes compiler)
Any ideas what is going wrong here?
Thanks,
Rahul.

How about using javac?

FLEX debugger not hitting breakpoints, because Flash sometimes embeds source file paths with wrong letter case?

I was trying to figure out why breakpoints were working fine for source files in some locations but not others. FlashDevelop's debugger (which I believe is actually the FLEXSDK debugger) was successfully connecting, tracing output, and hitting breakpoints in SOME files, but not others.
I downloaded SWFInvestigator from Adobe Labs and checked the embedded debug paths for various source files to see what was going on.
I discovered that files in which no breakpoints could be hit had their paths embedded in all lowercase (e.g. "c:\users\username\desktop\source\myproject" instead of "C:\Users\username\Desktop\source\MyProject").
So I have two questions:
First, is this a Flex debugger issue, or a FlashDevelop plugin issue? Letter case shouldn't matter or interfere with matching file paths in Windows.
Second, what could possibly influence the letter case of embedded paths in a SWF output by Flash Professional (CS6), such that they are sometimes all lowercase and other times maintain the same case from the file system? And why would that affect a debuggers ability to hit breakpoints in Windows 7? I am compiling in multiple ways. Sometimes clicking Publish within Flash. Sometimes the file being published is not even open in Flash, and my JSFL script file is passed to Flash.exe containing embedded file paths to open the document. Usually, everything seems to work fine, no matter where I publish from, regardless of whether the FLA file is open or not. I'm honestly starting to believe that it depends on how the FLA was last opened in Flash Professional, as though it saves some sort of last access path internally and uses that to embed debug information.

I don't think it's the source path in my case, because it's simply the dot ".", although I did check that because it would most likely influence the embedded paths.
In the library path, I use relative paths exclusively, since all my individual project folders exist in the same "source" folder.
Here's how I arrived at the conclusion that something more complex or "stateful" must be occuring:
I publish my files with a one-click application, which does the following
updates version timestamps (static constants) in specific files via regex match
fills in a JSFL template with the FLA filename and writes the JSFL file to disk, then passes the JSFL file path to flash.exe for publication
the JSFL then runs a command, which signals the main application via cross-process communication that the script has finished publishing
That all makes it easy for me to update and publish multiple projects and deploy them, with a single click. Here is the JSFL template I created, which has been drastically simplified since the days where it used to search to see if the file was open in Flash, select the document, and call publish. Now it just uses the publishDocument method to silently publish files without opening them.
var filepath = "FLAFILEPATH"; //template parameter: the URI (beginning with "file:///") of the FLA file to publish
fl.publishDocument( filepath, "PUBLISHPROFILENAME" );
FLfile.runCommandLine("COMPLETECOMMAND");
The C# app replaces the strings in all caps with the actual values. The COMPLETECOMMAND is actually populated with the application's own executable path, along with a "complete" switch, which lauches a 2nd instance, which handles the complete switch by broadcasting a signal over an interprocess channel and then terminates. The main instance captures the signal, triggers a wait handle, and continues with publishing the next file. Here is the core code for it:
private string fillTemplate( string fla_directory, string fla_filename, string publish_profile_name )
    string fileuri = "file:///" + Path.Combine( fla_directory, fla_filename ).Replace( '\\','/' );
    return EmbeddedResources.OpenAndPublish //JSFL template file embedded as string resource
        .Replace( "FLAFILEPATH", HttpUtility.JavaScriptStringEncode( fileuri ) )
        .Replace("COMPLETECOMMAND", HttpUtility.JavaScriptStringEncode( "\"" + Application.ExecutablePath + "\"" + " -publishcomplete" )) //call self with -publishcomplete switch to signal main instance's publishCompleteSignal
        .Replace("PUBLISHPROFILENAME", HttpUtility.JavaScriptStringEncode( publish_profile_name ) );
private static readonly string FLASH_PATH = @"C:\Program Files (x86)\Adobe\Adobe Flash CS6\Flash.exe";
public void publish( string fla_directory, string fla_filename, string publish_profile_name )
    Program.publishCompleteSignal.Reset();
    string template = fillTemplate( fla_directory, fla_filename, publish_profile_name );
    string curdir = Environment.CurrentDirectory;
    string tempJSFLfilepath = Path.Combine( curdir, "temp_script.jsfl" );
    File.WriteAllText( tempJSFLfilepath, template );
    Process p = Process.Start( FLASH_PATH, tempJSFLfilepath );
    Program.publishCompleteSignal.WaitOne( 30000 ); //timeout after 30 seconds
Here's where it gets interesting. The FLAFILEPATH has ALWAYS been passed in as all lower case, yet this publication method has worked 99% of the time for hundreds of publish operations every day. This applies to both the publication of the first SWC, which is referenced by the second published SWF (both were being published with lowercase paths), yet the paths for the main SWF were remaining in lowercase, while those in the referenced SWC were maintaining the correct case from the file system.
So there may be any number of things going on here. SWCs may be published differently than SWFs, such that SWCs always have the correct letter case for debug source files, regardless of how the source FLA project was opened. Ensuring the path passed to publishDocument uses the right case definitely fixes the problem, but it doesn't explain why it usually worked, despite having always been passing a lowercase string. The only variable I can think of in all of this is Windows itself or Flash, such as whether the document was open in Flash at the time the silent JSLF publishDocument command ran, and how that FLA was last opened (via shortcut, via "recent documents" in Flash, via recent documents in Windows. It has to be something, even if it's something as obscure as how the folder path was last accessed in windows, although I strongly suspect it's just how (in terms of path case) the FLA was last opened in Flash.
In any case, I'm happy that passing the right case to JSLF's publishDocument command fixes the problem, so I'm not going to spend any more time trying to figure out how opening the FLA in various ways could affect the embedded debug paths. The only thing that should be done is to address how paths with the wrong case are handled when they do get embedded that way for whatever reason. Perhaps the flex debugger should be updated to use case-insensitive matches in case-insensitive file systems, unless, perhaps, this is a FlashDevelop debugger issue after all.

Code behaves differently when run in debugger

var he:Array = handControl.getHumanInfo(ha, handNumber);
while (he.length != 0)
humanInfo.push(he.shift());
This snippet is part of a large flash project I am working
on. The program works fine by itself, but when I try to step
through it in the debugger, it sometimes crashes, depending on
where I put a breakpoint. If I put the breakpoint on the first line
of code above, I can step into the function getHumanInfo(), trace
it, and step back out, and everything is fine. But if I only put a
breakpoint somewhere inside the getHumanInfo() function, all of a
sudden when I step out of that function, the variable 'he' is
undefined, and so the while loop never ends.
This makes no sense to me. The code is either good or bad, it
shouldn't behave differently based on where I put the breakpoint.
The getHumanInfo() function always creates a new array and
passes it back, so there is no reason 'he' should be undefined.
This has happened many times when I've tried to use the flash
CS3 debugger -- is there a known issue that this sounds like? I'm
so fed up I'm ready to stop using the debugger altogether.

I ran the program without the debugger and put some trace()
statements in, just to make sure. Everything works fine without the
debugger. So it seems to me it has to be a debugger issue. Has
anyone heard of a similar issue?

Std::bad_alloc occurs only when using VS Graphics Debugger

I'm using C# and SharpDX (a c# wrapper for directx) and I keep getting the following exception when using the Graphics Debugger in VS2012 and VS2013:
First-chance exception at 0x7690c41f in Craft.exe: Microsoft C++ exception: std::bad_alloc at memory location 0x3276eda4.
A first chance exception of type 'System.Runtime.InteropServices.SEHException' occurred in SharpDX.Direct3D11.dll
An exception of type 'System.Runtime.InteropServices.SEHException' occurred in SharpDX.Direct3D11.dll but was not handled in user code
Additional information: External component has thrown an exception.
I have native code debugging enabled and I'm using the directx debug device. The program runs fine normally, but when I use the graphics debugger, I get this exception almost all the time, usually pretty late in the loading phase. When it happens,
it highlights this line of code:
newVertexBuffer = new Buffer(Engine.Device, VertexDataStream, (int)VertexDataStream.Length, ResourceUsage.Immutable, BindFlags.VertexBuffer, CpuAccessFlags.None, ResourceOptionFlags.None, 0);
Like I said, this happens quite late into the loading phase, at which point this line of code has run hundreds of times successfully, and works just fine when not using the graphics debugger. Is this a bug/issue with the VS debugger or something?

Hi,
Welcome to MSDN.
The default memory allocation is the debugger heap, not the Debug CRT heap while running Visual Studio Debugger.
It can be slow if we allocate/free a lot of memory, since it will cost lots of time on this special heap.
You could refer to this
thread and this
link to get more information. There is a detailed description of debugger heap shared by “MSN” (his user name) in this
link.
In order to solve this issue, we could disable the debug heap as following steps:
Control Panel->System Properties->Advanced System Settings->Environment Variables->System Variables.
Add a new Variable called “_NO_DEBUG_HEAP” with a value of “1”.
In addition, I suggest you post this issue in this forum below:
http://xboxforums.create.msdn.com/forums/76.aspx
like this thread “Visual Studio 2012 Graphics Debugger Issue”,
since there are a lot of developers with more professional knowledge can help you.
Thanks for your understanding.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Connection to the Debugger or Profiler could not be established

I think I have a Flex/Flash Builder beta config issue? Would be very grateful for any advice.
This might be a good clue to source of my problem: If I run Flash CS4 Professional and "Begin Remote Debug Session" the flash player will connect to the CS4 debugger - and this is running the same project file in either IE8 or Firefox 3. But it will not connect with the Flex debugger.
I'm in Windows XP and just trying to learn Flex with the "learn in a week" exercises but spent about a fuggin day trying to fix the debugger issue. I've done everything that the forums advise: checked localhost is 127.0.0.1, checked the mm.cfg, reinstalled everything browsers, flash debug versions.. but still can't get the damn debugger in Flex or now Flash Builder beta to work.
Somebody please help!
Robert

In the case of Flash Professional, a connection is established between the Flash Player Debug version and the Flash Professional Debugger while running the swf (whether local or published on a web server). You right click on the Flash area in the browser and select remote debug.
In the case of Flex, a connection is established between the local swf that has just been built in debug mode (in bin-debug) and the Flex Builder Debugger (or Profiler).
If you want to run the Flex Debugger or the Flex Profiler, launch the application from Flex Builder in Debug mode or in Profiler mode respectively. Do not try to publish your swf on a web server, right click and select remote debug as you do in Flash Professional. It won't work.
I have also found I coult only make the Profiler work in IE, not in Firefox.

FB4.6 debugger issue

Similar Messages

Maybe you are looking for