| Newbie: Eclipse/Qt/MinGW gdb failure [message #530173]
||Wed, 28 April 2010 17:54
| CJ Roth
Registered: April 2010
Please help - I am unable to run any program in debug mode in Eclipse.|
I recently installed Eclipse for C/C++ (build 20100218-1602), Qt (2010.02.1), MinGW (5.1.6, but with gcc updated to 4.5.0), Msys 1.0.11, and MinGW gdb v7.1.2 on a Windows XP Pro Sp3 machine.
I was able to build the AddressBook application from the QT tutorial. It runs fine in 'normal' mode, but in debug mode, it fails with the message "gdb: unknown target exception 0xc0000135 at 0x7c9666c6". The same error code is reported when trying to run other programs in debug mode within Eclipse.
In a command prompt window, I can run the AddressBook application in 'gdb' without any problem, but that defeats the whole purpose of trying to debug it within Eclipse.
In perusing the forums here, I have found entries from other people with this same exact issue. They were able to solve it by adding library path specifications to the PATH variable, but I've already done that. The only difference in my installation is that I have a newer version of gdb (7.1.2) and gcc (4.5.0).
The relevant lines from the gdb output in the Eclipse console are :
gdb-set environment LIBRARY C:\MinGW\lib;C:\qwt-5.2.1\lib;C:\Qt\2010.02.1\bin;C:\msys\1. 0\lib
gdb-set environment Path C:\MinGW\lib;C:\qwt-5.2.1\lib;C:\Qt\2010.02.1\qt\bin;C:\msys \1.0\lib;C:/Program Files/Java/jre6/bin/client;C:/Program Files/Java/jre6/bin;C:\MinGW\bin;C:\WINDOWS\System32
gdb: unknown target exception 0xc0000135 at 0x7c9666c6
I'm at my wit's end. I've tried adjusting the order of the PATH library specifications, but nothing has helped.
Any other library specifications that I should add to the list?
My only other option I see right now is to downgrade the gcc installation to 4.4, matching the others who were able to successfully overcome this 0xc0000135 error hurdle.
Powered by FUDForum
. Page generated in 0.05354 seconds