| Debugger error in makefile project from existing code [message #1828856] |
Sat, 20 June 2020 05:00  |
 xiaolei cui
Messages: 12
Registered: June 2020 |
Junior Member |
|
|
Hi all,
This is an update from the previous post on GDB error. I am using eclipse CPP on Windows7 and 10, with mingw toolchain.
When I try to debug a makefile project (from existing code), I keep getting error message, debugging cannot start:
Error in final launch sequence:
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000139.
The error code on some computer is 0xc0000135.
Debegging with GDB works well as I create a C project from scratch.
Debugging with GDB shipped with mingw works fine in command line.
So this is unlikely due to missing dll or gdb fault.
Any ideas would be appreciated!! The older versions of Eclipse CPP have the same issue, How to report a bug for eclipse CDT?
thanks.
xiaolei
[Updated on: Sat, 20 June 2020 06:34] Report message to a moderator |
|
|
|
|
|
| Re: Debugger error in makefile project from existing code [message #1828920 is a reply to message #1828891] |
Mon, 22 June 2020 12:20  |
David Vavra
Messages: 1426
Registered: October 2012 |
Senior Member |
|
|
(1) and (3) point toward a configuration problem.
An example would be one that seems common regarding 0xc0000135: the wrong .NET version.
if (3) works but (1) doesn't then comparing the differences seems indicated.
(1) sounds like an over-generalization.
It shouldn't matter who generated the makefile.
However, there could be something in the makefile which is causing the problem.
Regarding (2): not sure what an empty-executable C project is.
One without an executable?
If so, how do you launch anything?
It's not GDB/MI and Eclipse, it's GDB/MI by itself and only when it tries to start the program to be debugged.
To properly locate the cause you need an interface to GDB using MI that is different than Eclipse.
It's doubtful that anyone other than yourself can look into this issue.
How would anyone duplicate it without having your software and system configuration?
Eclipse is executing the program reporting the problem.
It's doubtful that Eclipse is involved in the cause.
[Updated on: Mon, 22 June 2020 12:21] Report message to a moderator |
|
|
| Re: Debugger error in makefile project from existing code [message #1828927 is a reply to message #1828920] |
Mon, 22 June 2020 13:43 |
xiaolei cui
Messages: 12
Registered: June 2020 |
Junior Member |
|
|
Hi David,
let me restate point (2), it is misleading:
it works well if I step through new project - C/C++ - C proejct - executable - empty project (with mingw), and then create a simple project justs to test debugging.
But debugging will fail to start if I create project by stepping through : new project - C/C++ - makefile project with existing code, after importing I just build the project and set the debugging arguments ready. So on the same computer ,using the same IDE, this what really happens.
THanks for the hints, I will check the .net framework version.
One thing I want to mention is that if the debugging feature of Eclipse CPP sometimes functions well , sometimes not, it is probably worth to find the cause the fix it.
[Updated on: Thu, 25 June 2020 02:34] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03131 seconds
] 
Search
Help
Register
Login
Home
