Comment 1 Johann Duscher 2011-03-18 03:54:04 EDT

I'm experiencing the same problem:

------------------
An internal error occurred during: "Launching Core-C++ Debug_Test".

java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key AbstractCLaunchDelegate.Program_is_not_a_recognized_executable
at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
at java.util.ResourceBundle.getString(ResourceBundle.java:334)
at org.eclipse.cdt.dsf.gdb.launching.LaunchMessages.getString(LaunchMessages.java:44)
at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.verifyBinary(LaunchUtils.java:157)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.checkBinaryDetails(GdbLaunchDelegate.java:232)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:124)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:83)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:72)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
------------------
Eclipse version info:

eclipse.buildId=2.5.2.201102261000-SR1
java.version=1.6.0_24
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=de_DE
Framework arguments:  -product com.springsource.sts.ide -product com.springsource.sts.ide -product com.springsource.sts.ide -keyring /Users/xxx/.eclipse_keyring -showlocation
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product com.springsource.sts.ide -product com.springsource.sts.ide -data /Users/xxx/workspace-sandbox-cpp -product com.springsource.sts.ide -keyring /Users/xxx/.eclipse_keyring -showlocation
------------------

I found a blog page which suggests to build 32-bit executables (http://blog.christianleberfinger.de/?p=167), but this doesn't work for me.

This is really annoying and renders C++ development using Eclipse nearly unusable. I need to go back to old "printf" (or "cout" if you want) style debugging...

Comment 2 mwolf 2011-04-13 08:59:16 EDT

Proposed solution: Define toolchain for your c++ project

I had exactly this error situation until I have defined a valid toolchain in my project properties ( right click on project -> Properties -> C/C++ Build -> Tool chain editor).

After I had defined a toolchain ( I am working with Cygwin GCC ), debug session starts as expected.

Comment 3 Steven Bluen 2011-05-02 03:59:35 EDT

(In reply to comment #2)
> Proposed solution: Define toolchain for your c++ project
> 
> I had exactly this error situation until I have defined a valid toolchain in my
> project properties ( right click on project -> Properties -> C/C++ Build ->
> Tool chain editor).
> 
> After I had defined a toolchain ( I am working with Cygwin GCC ), debug session
> starts as expected.

And what did you do after going to the toolchain editor? I am using MinGW and no matter what I do, the toolchain editor doesn't solve the problem for me with MinGW.

Comment 4 Michael Osipov 2011-05-30 04:16:53 EDT

Just stumbled upon this issue and tackled it down.
Open this file: eclipse\plugins\org.eclipse.cdt.dsf.gdb_3.0.0.201102110609.jar
got to \org\eclipse\cdt\dsf\gdb\launching\LaunchMessages.properties
Rename property 'AbstractCLaunchDelegate.Program_is_not_a_recongnized_executable'
to 'AbstractCLaunchDelegate.Program_is_not_a_recognized_executable'
and the problem should be gone.

This is simply a typo. A superfluous n.

Comment 5 Michael Osipov 2011-05-30 04:37:18 EDT

Moreover, I cloned the git repo and the bug in present in tag CDT_7_0_2, branch cdt_7_0_1 but gone in the master branch. We have to wait for an upstream version.

Comment 6 Marc Khouzam 2011-05-30 09:11:40 EDT

(In reply to comment #5)
> Moreover, I cloned the git repo and the bug in present in tag CDT_7_0_2, branch
> cdt_7_0_1 but gone in the master branch. We have to wait for an upstream
> version.

The typos was fixed in Bug 335776 for the next CDT release.

However this is not the real problem, it is just that the error message cannot be printed properly.  But the error is that "Program_is_not_a_recognized_executable", so the people seeing this issue don't have a properly built executable.

You may want to try doing a Clean on your project and building again.
You may also want to try to run the executable from the command line to see if it is a proper executable.

This is most probably a configuration problem and not an eclipse bug.

If I'm wrong, please re-open.

Comment 7 temporarypleasediscard 2011-06-16 07:41:50 EDT

This was driving me crazy - I was trying to get Eclipse CDT v7.0.2 working on Windows 7 (32-bit Helios on 64-bit machine) with MinGW and GDB.

The program would RUN but it wouldn't DEBUG (giving the AbstractCLaunchDelegate.Program_is_not_a_recognized_executable problem described).

Then I found this link:
  http://www.codeproject.com/KB/tips/CPP_Dev_eclipse_CDT.aspx

All I had to do was go:
  Project -> Properties -> C/C++ Make Project -> Binary Parser
and TICK
  PE Windows Parser

I also ticked "Elf Parser" and unticked all others (so "GNU Elf Parser" was also unticked).

Suddenly interactive debugging started working! Great!

Created dummy bugzilla account just to post this solution to my problem in case it helps anybody else in future.

Comment 8 Joshua Richardson 2011-12-06 16:34:42 EST

Thank you very much!

On the Mac, I selected "Mach-O 64 Parser" to make it work!