9

If I run debugger then it gets stuck on 89% process... It shows 

 Launching : Configuring GDB Aborting configuring GDB

I just wanted to see the debugger is working so all I have is

printf("debug test");

in main function.. Do you guys know what the problem is?

codereviewanskquestions
  • 13,460
  • 29
  • 98
  • 167
  • Did you use cdt on which platform? – Kane Mar 25 '11 at 06:04
  • 2
    @LCYSoft Currently I have issue with the same symptoms. Whenever I start debugging even simple Java app in eclipse, progress goes to 89% and nothings happens after that. It seems that you have solved this issue. Could you say: where can I download this libexpat-1.dll, where should I place it and how can I check that problem appears because of this DLL? – Andrei Botalov Jun 09 '12 at 12:29

4 Answers4

9

I have spent quite some time on this. It's really annoying and the solution is stupid to me:

Environment:

Mac + Eclipse + gdb (ggdb downloaded from macports).

Symptom:

Debugging hangs at 100% at startup. launching gdb aborting configuring gdb.

Solution: run as root

sudo /Applications/Eclipse.app/Contents/MacOS/eclipse

Armstrongest
  • 15,181
  • 13
  • 67
  • 106
MarcoWood
  • 91
  • 1
  • 2
  • 1
    +1 worked for me too. I guess that sudo is not the best solution here. Maybe theres just a certain group membership you would have to have as the resp. user in order for it to work. – col.panic Aug 25 '17 at 09:36
  • For me eclipse is installed in /Users/[Username]/eclipse/cpp-oxygen/Eclipse.app Thank you! – Mykola Servetnyk Aug 17 '18 at 06:08
2

I believe the answer lies in codesigning, and the problem originates with the system security changes introduced by Apple. Please see this Stack Overflow answer, which fixed the same issue for me. Launching Eclipse with sudo (as recommended above) should probably be discouraged due to potential risks with your IDE going haywire with root permissions.

lcary
  • 393
  • 2
  • 13
  • I've signed the gdb executable (and verified it with `codesign --verify --verbose ./arm-none-eabi-gdb`), however, it still doesn't work, still the same error... – Danijel Sep 11 '19 at 17:08
1

I also encountered this error on Mac Mavericks. After which gdb I figured out that the path set in Eclipse Debug Configuration is not correct. Somehow I mistakenly set it to /usr/local/bin/gdb which actually should be /usr/bin/gdb

BabyPanda
  • 1,562
  • 12
  • 18
1

hello after experiencing the same, it appeared gdb was missing access to some dll (libexpat-1.dll). putting it in the current path corrected the problem. in order to check this, try invoking gdb from the command prompt

all the best

olivier

olivier
  • 26
  • 1