Bug 552912 - GDB debugging doesn't work with Windows10 using cygwin
Summary: GDB debugging doesn't work with Windows10 using cygwin
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 9.8.0   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-11 12:07 EST by Kanagarajan Palaniappan CLA
Modified: 2019-11-11 13:04 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kanagarajan Palaniappan CLA 2019-11-11 12:07:16 EST
Unable to get the GDB working using the example HelloWorld C++ application.
Get these below errors

Error in final launch sequence:

Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
During startup program exited with code 0xc0000135.


Also the same issue noticed in the latest build:

Eclipse IDE for C/C++ Developers
Version: 2019-09 R (4.13.0)
Build id: 20190917-1200
OS: Windows 10, v.10.0, x86_64 / win32
Java version: 1.8.0_231

PATH variable setup :
${CYGWIN_HOME}  C:\cygwin64
${CYGWIN_HOME}\bin;//and other jre tools path.

I was able to compile and run the application and also able to run cygwin gdb from command line.
Comment 1 Jonah Graham CLA 2019-11-11 13:04:25 EST
I believe that this problem is caused by the environment that Eclipse is launching in not having all the path information needed to launch successfully. Perhaps you can confirm by starting Eclipse from inside the working Cygwin command line environment, that will make Eclipse inherit the Cygwin environment fully.

If that solves the problem, you can report what is different about the environments and perhaps CDT can do something with that. IIRC someone had reported that there may be a problem of Path vs PATH environment variables - CDT should be treating them the same on Windows.

Please let me know what you find and we can proceed from there.