MacOS – Could not determine GDB version using command: sudo /usr/local/bin/gdb –version

eclipsemacbook promacosterminal

Eclipse (Mars) version (C programming language):
Eclipse IDE for C/C++ Developers
eclipse.buildId=4.5.0.I20150603-2000

MacOS version:
OS X Yosemite 10.10.3
HW: MacbookPro 15" (mid-2015) Retina

Problem:
Debug action causes following error message ("111" is both Project Name, and source 111.c file as well):

window title: "Problem Occurred"
Error message:
'Launching 111' has encountered a problem.
Could not determine GDB version using command: sudo /usr/local/bin/gdb –version
sudo: no tty present and no askpass program specified

As far as I understand – that GBD module was removed from MacOS X, so I probably need to install manually one.
I am newcomer in Mac, and trying installing upon different forums – I didn't succeed yet.

Probably, there maybe changes required as well in:

Debug Configurations (Run->Debug Configuration->"Debugger" tab).
Or/and as well in:
Eclipse -> Preferences -> C/C++ -> Debug -> GDB

Please answer me – who installed recently by him-/her- self. Since old (more than year from now) forums may describe other case compared to problem I need to solve.

Please provide exact steps how to manage.

Best Answer

Install with MacPorts

Install Xcode and MacPorts, if not already installed.
Now install the Apple GCC and GDB from MacPorts:

$ sudo port install gdb-apple $ sudo port install apple-gcc42

Install with Homebrew

Install Xcode and Homebrew, if not already installed.
Now install GDB from Homebrew:

$ brew tap homebrew/dupes $ brew install gdb

Source: http://ntraft.com/installing-gdb-on-os-x-mavericks/

Related Solutions

How to undo overwriting the /usr/local/bin folder

Well, it's not a complete disaster. You could have done it to /usr/bin. The obvious first answer is restore it from a backup. If you don't have a backup then you can take some comfort in the fact that the /usr/local/bin directory isn't in the default search path for command-line executables without extra steps being taken so the damage you've caused is likely to be limited. Really, without a backup all you can do is reinstall apps which had files there. Without knowing what they were, you'll probably need to wait for apps to misbehave or crash and then you can try a reinstall to see if that fixes them. Hopefully you have Time Machine set up in which case it's a simple matter of following the procedure below:

Open Terminal to run the following commands
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder - this restarts Finder so it will show the hidden system files
Open a Finder window for your Hard Drive
Open usr, then local, then bin
Launch Time Machine
With the bin folder selected, scroll back in time in the time machine interface to your last successful backup of the /usr/local/bin folder and click restore in the bottom-right corner
In a few moments, your folder will be restored.

Also, in future be very careful what you do with sudo and especially sudo mv. You can use sudo mv -i mvim /usr/local/bin/mvim and the -i will warn you instead of just overwriting whatever it finds at /usr/local/bin/mvim.

After you're done, you can hide the hidden files again by running the following commands in Terminal

defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder

Amending PATH so that /usr/local/bin is ahead of /usr/bin

Yes, create a .bash_profile file in your home directory containing

PATH="/usr/local/bin:$PATH"

and then do one of the following to make the change active

execute . ~/.bash_profile
execute PATH="/usr/local/bin:$PATH" in the current shell
restart Terminal