Eclipse Community Forums: C / C++ IDE (CDT) » Unable to debug with Neon and TDM-GCC

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » Unable to debug with Neon and TDM-GCC

Show: Today's Messages :: Show Polls :: Message Navigator

Unable to debug with Neon and TDM-GCC [message #1774965]

Mon, 23 October 2017 01:04

Bruce Kelly

Messages: 5
Registered: October 2014

Junior Member

Windows 7 64-bit
Eclipse Neon.2 (4.6.2) 64-bit
TDM-GCC 5.1.0-2 64-bit

When I try to debug a C program I get the following error:

Could not determine GDB version using command: C:\TDM-GCC-64\bin\gdb.exe --version
gdbwrapper: AssignProcessToJobObject failed

If I run the same command from the command line I get:

C:\Windows\System32>C:\TDM-GCC-64\bin\gdb.exe --version
GNU gdb (GDB) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http...
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http...
Find the GDB manual and other documentation resources online at:
http...
For help, type "help".
Type "apropos word" to search for commands related to "word".

I can debug from the command line, but it would be easier if I could do it in Eclipse.

Any assistance would be appreciated.

There is an entry in the Eclipse log:
java.lang.Exception: gdbwrapper: AssignProcessToJobObject failed

at org.eclipse.cdt.dsf.gdb.launching.GdbLaunch.getGDBVersion(GdbLaunch.java:559)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:142)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:101)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:90)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[Updated on: Mon, 23 October 2017 09:57]

Report message to a moderator

Re: Unable to debug with Neon and TDM-GCC [message #1778404 is a reply to message #1774965]

Wed, 13 December 2017 20:58

Jesse Hopkins

Messages: 1
Registered: December 2017

Junior Member

Bruce,

Did you ever resolve this? I am hitting the exact same problem today with Oxygen, TDM-GCC using gdb 7.9.1.

As you said, I can start gdb manually from a command prompt just fine, but when attempting to start a debug session from Eclipse, it fails with an error message:

Could not determine GDB version using command: C:\TDM-GCC-64\bin\gdb.exe --version
gdbwrapper: AssignProcessToJobObject failed

Report message to a moderator

Re: Unable to debug with Neon and TDM-GCC [message #1778534 is a reply to message #1778404]

Fri, 15 December 2017 21:49

Bruce Kelly

Messages: 5
Registered: October 2014

Junior Member

Unfortunately I haven't managed to do so.

I suspect it is something to do with the output from the command.
I was going to check the source code but I couldn't find a packaged version of the source and I didn't want to download the complete repository.

I have downloaded Oxygen and I get the same result, which is what I expected.

One thing I haven't tried is to see if I could find a different compiled copy of gdb.
I'm not sure if the output from the command was changed when TDM compiled it.

Namaste, Bruce

Report message to a moderator

Re: Unable to debug with Neon and TDM-GCC [message #1794167 is a reply to message #1778534]

Fri, 24 August 2018 21:52

Ronglin Zhao

Messages: 1
Registered: August 2018

Junior Member

In the Eclipse Debug configuration, at the "Debugger" tab, try C:\MinGW\gdb64\bin\gdb.exe for GDB debugger. The default C:\MinGW\bin could be 32-bit.

Report message to a moderator

Re: Unable to debug with Neon and TDM-GCC [message #1794237 is a reply to message #1794167]

Mon, 27 August 2018 21:50

Bruce Kelly

Messages: 5
Registered: October 2014

Junior Member

I think TDM is 64 bit only, but using "gdb -version" in both directories gives the same result:

C:\TDM-GCC-64\gdb64\bin>gdb.exe -version
GNU gdb (GDB) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

Report message to a moderator

Previous Topic:	[SOLVED] No Output in Console
Next Topic:	GCC extension types

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jan 19 12:47:15 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter