I’ve run into two separate versions of this issue. Basically, when debugging an application with CDT the application automatically breaks at the entry point to main(). The first version is easy to fix. Open the Debug Configurations dialog for the project, select the Debugger tab and uncheck the “Stop on startup at:” checkbox. The second version is a little less obvious and is usually accompanied by an uninformative stack trace similar to this:
Thread [1] (Suspended) 7 ntdll!RtlFindSetBits() 0x7768fc02 6 ntdll!RtlFindSetBits() 0x7768fc02 5 ntdll!TpReleaseCleanupGroupMembers() 0x776abd90 4 <symbol is not available> 0x00000050 3 <symbol is not available> 0xffffffff 2 <symbol is not available> 0x0028ef30 1 0x00000000
The not so obvious solution to this is to again, go to the project Debug Configuration dialog, select the Debugger tab, select the Shared Libraries tab and uncheck the “Load shared library symbols automatically” checkbox. https://www.eclipse.org/forums/index.php/m/493210/
- The Art of Debugging with GDB, DDD, and Eclipse
- Eclipse For Dummies (For Dummies (Computer/Tech))
- C/C++ Software Development with Eclipse: An easy to understand yet thorough guide on using Eclipse for C/C++ Software Development.
]]>