Skip to main content


Eclipse Community Forums

      Home
Home » Language IDEs » C / C++ IDE (CDT) » Debugger dies during initialization on OSX 10.6
Debugger dies during initialization on OSX 10.6 [message #1098233] Fri, 30 August 2013 16:34 Go to next message
Eclipse UserFriend
Hi

When I try to debug my app with the debug launch command I get this trace:
Thread [1] (Suspended : Breakpoint)	
	__static_initialization_and_destruction_0() at iostream:77 0x10000250e	
	global constructors keyed to VisualAsset.cpp() at VisualAsset.h:31 0x100002547	
	__dyld__ZN16ImageLoaderMachO18doModInitFunctionsERKN11ImageLoader11LinkContextE() at 0x7fff5fc0d500	
	__dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEj() at 0x7fff5fc0bcec	
	__dyld__ZN11ImageLoader15runInitializersERKNS_11LinkContextE() at 0x7fff5fc0bda6	
	__dyld__ZN4dyld24initializeMainExecutableEv() at 0x7fff5fc0210e	
	__dyld__ZN4dyld5_mainEPK12macho_headermiPPKcS5_S5_() at 0x7fff5fc06981	
	__dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKcl() at 0x7fff5fc016d2	
	__dyld__dyld_start() at 0x7fff5fc01052


This is before the main is called.
I link with SDL, OpenGL and Cocoa and also include boost headers, if that matters.

Debugging with gdb from command line works normally.
Any ideas?
thanks
David
Re: Debugger dies during initialization on OSX 10.6 [message #1099906 is a reply to message #1098233] Mon, 02 September 2013 07:17 Go to previous messageGo to next message
Eclipse UserFriend
I guess you are missing some libs which are needed at runtime (libSDL.so etc.). You need to put the libs in /usr/lib (or whereever OS X looks for libs). Or you can modify the LD_LIBRARY_PATH environment variable directly in your launch debug configuration.
Re: Debugger dies during initialization on OSX 10.6 [message #1101262 is a reply to message #1099906] Wed, 04 September 2013 04:15 Go to previous message
Eclipse UserFriend
Thanks, it's true, nothing is on the LD(DYLD) lib path.
But all dependencies are linked as "frameworks" (actually I have no idea what that means).
But if this is the problem, how come that gdb works as-is? I didn't set the library path in console either...
Previous Topic:[SOLVED] debugger suddenly stopped working
Next Topic:/bin/sh: arm-none-linux-gnueabi-g++: not found
Goto Forum:
  


Current Time: Sat May 24 07:04:56 EDT 2025

Powered by FUDForum. Page generated in 0.02892 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly