Eclipse Community Forums: C / C++ IDE (CDT) » What is the output file extension for builds (Indigo running on a MAC)?

Home » Language IDEs » C / C++ IDE (CDT) » What is the output file extension for builds (Indigo running on a MAC)?

What is the output file extension for builds (Indigo running on a MAC)? [message #697255]

Fri, 15 July 2011 18:55

Eclipse User

Hi - this is a repost from an earlier thread that I'm trying to get answers to.

I have CDK toolchain, as well as other software (see original post), and I'm trying to build and debug a very simple C program in eclipse Indigo (running on a Mac, if that makes any difference). The program runs fine, but when I try to debug it, it says the "Program is not a recognized executable", and hence my question:

I noticed the output file for both the release and debug builds have no extensions. I'm thinking I'm getting the above error message due to a missing extension on the output file name. (correct me if this is not the case - the program "runs" fine). Anyway, I checked the default extensions for binaries are .exe, .elf. and .out. Does anyone know what the extension should be for an output file, if any, when running eclipse on a Mac? How come these builds do not put an extension on the output file? Do you know where that would be set in Eclipse?
Thanks,
Will

See the original thread for a complete description of the issue (posted by me on July 12, 2011) or by searching for message (post#) 696000

Re: What is the output file extension for builds (Indigo running on a MAC)? [message #698186 is a reply to message #697255]

Mon, 18 July 2011 20:29

Eclipse User

It doesn't need an extension, the Macho parser should detect it as a binary without an extension. CDK toolchain, where is it from? Binary parsers are set in the target platform of the toolchain, maybe this toolchain doesn't have a Mac version with the binary parser specified. So you might need to enable it manually. Right-click on your project, C/C++ Build, Settings, Binary Parsers, select Mach-O 64 Parser (it handles powerpcc, Intel 32 and 64 bits).

Re: What is the output file extension for builds (Indigo running on a MAC)? [message #699652 is a reply to message #698186]

Thu, 21 July 2011 22:17

Eclipse User

You're a genius! It worked! I only had "elf parser" selected and MACH-O 64 Parser was not selected. You would think the CDK toolchain would have a binary parser that it needs to run on a Mac, as Macs are somewhat popular (not as much as PCs), and I downloaded eclipse Indigo for Mac.
Thank you!!!
Will

Also, just out of interest, here are all toolchain software I downloaded:

C/C++ Development Tools 8.0.0.201106081058 org.eclipse.cdt.feature.group Eclipse CDT
C/C++ Development Tools SDK 8.0.0.201106081058 org.eclipse.cdt.sdk.feature.group Eclipse CDT
C/C++ GNU Toolchain Debug Support 7.1.0.201106081058 org.eclipse.cdt.gnu.debug.feature.group Eclipse CDT
C/C++ Library API Documentation Hover Help (Incubation) 0.3.0.201106060936 org.eclipse.linuxtools.cdt.libhover.feature.group Eclipse Linux Tools
Eclipse Debugger for C/C++ 2.0.0.201106081058 org.eclipse.cdt.debug.edc.feature.group Eclipse CDT
Eclipse IDE for C/C++ Developers 1.4.0.20110615-0550 epp.package.cpp null

Re: What is the output file extension for builds (Indigo running on a MAC)? [message #765600 is a reply to message #699652]

Wed, 14 December 2011 06:11

Eclipse User

Hello,

"The program runs fine, but when I try to debug it, it says the "Program is not a recognized executable", ....."

I'm also facing same issue for Windows OS.
Kindly let me know what setting I need to do, to avoid this problem?

Re: What is the output file extension for builds (Indigo running on a MAC)? [message #766133 is a reply to message #765600]

Thu, 15 December 2011 04:07

Eclipse User

VGG wrote on Wed, 14 December 2011 12:11

Hello,

"The program runs fine, but when I try to debug it, it says the "Program is not a recognized executable", ....."

I'm also facing same issue for Windows OS.
Kindly let me know what setting I need to do, to avoid this problem?

You have to select the PE binary parser.

Re: What is the output file extension for builds (Indigo running on a MAC)? [message #768575 is a reply to message #766133]

Tue, 20 December 2011 06:53

Eclipse User

Hello,

Thanks Mueller for your reply.

My problem is yet not resolved as I'm not aware, as to where I've to make this change.
I'm very new to eclipse. So, please help me out.

I want to deug a remote Unix box from my Windows host PC. For that I was able to run [setting from "Run As" mode] remote application from host PC with zero error. It also shows my application output on console window. But when I do same setting with "debug as" mode then it displays:

" Cannot run program 'gdb': Launching failed " Error.

I've perform following setting in "Debug As" mdoe:
1. Main Tab -> Using Standard Remote Create Process Launcher
2. Debugger Tab -> a.) Main Tab: debugger: gdb & command line: .gdbinit & Protocol: Default
b.) Gdbserver Settings: gdbserver & port: 22
3. Common Tab -> a.) Standard Input and Output: Allocate console
b.) Encoding: Default

I've tried to cover all important setting I did, to explain you my problem. Please let me know how I can resolve it.

Regards,
VGG

Re: What is the output file extension for builds (Indigo running on a MAC)? [message #768737 is a reply to message #768575]

Tue, 20 December 2011 12:19

Eclipse User

VGG wrote on Tue, 20 December 2011 12:53

Hello,

Thanks Mueller for your reply.

My problem is yet not resolved as I'm not aware, as to where I've to make this change.
I'm very new to eclipse. So, please help me out.

I want to deug a remote Unix box from my Windows host PC. For that I was able to run [setting from "Run As" mode] remote application from host PC with zero error. It also shows my application output on console window. But when I do same setting with "debug as" mode then it displays:

" Cannot run program 'gdb': Launching failed " Error.

I've perform following setting in "Debug As" mdoe:
1. Main Tab -> Using Standard Remote Create Process Launcher
2. Debugger Tab -> a.) Main Tab: debugger: gdb & command line: .gdbinit & Protocol: Default
b.) Gdbserver Settings: gdbserver & port: 22
3. Common Tab -> a.) Standard Input and Output: Allocate console
b.) Encoding: Default

I've tried to cover all important setting I did, to explain you my problem. Please let me know how I can resolve it.

Regards,
VGG

You need a local gdb installation that will talk with the gdbserver on the remote host. Please use the search function of this forum to get the a more detailed answer (this was asked several times before).

Previous Topic:	Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7
Next Topic:	includes and unresolved symbols problem on ubuntu

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 17 21:17:29 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter