Debugger not configured correctly

geotavros

PBarnes, you should be able to debug the application using GDB. But first you need to recompile your application with MinGW compiler. If you compile the application usin MSVC compiler you will not hit any breakpoints when debugging with GDB.

I also have the problem with CDB debugging. Windows 7 x64. I use Qt SDK where is Qt Creator (2.3.1) and Qt 4.7.4 x32. It says:

bq. The preferred debugger engine for debugging binaries of type ‘x86-windows-msvc2008-pe-32bit’ is not available.
The debugger engine ‘Gdb engine’ will be used as a fallback.
Details:There is no CDB binary available for binaries in format ‘x86-windows-msvc2008-pe-32bit’

I have MSVC 2008 installed.

geotavros

I've fixed the problem with CDB debugging by installing Debugging tools for Windows. I have downloaded this iso file (Windows SDK) for x64 Windows:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8442
And installed only the Debugging Tools. Now it works.

Benzin

Hello guys, (first post here, i been a programer for several years but im new to Qt ands im loving it ) :)
I had this exact same problem. not being able to debug if i build with msvc. did what geotavros sugested, and now i can debug fine! :)
Im still not clear thoug if this is a bug on QtCreator, or somehow my computer not having the windows debuger (seems unlikely since i have visual studio professional (including Visual C++) installed.
And another thing, is this related to the warning i get when i build using the vc compiler, as i explained here:
http://developer.qt.nokia.com/forums/viewthread/13925/

koahnig

[quote author="Benzin" date="1327926172"]Hello guys, (first post here, i been a programer for several years but im new to Qt ands im loving it ) :)
I had this exact same problem. not being able to debug if i build with msvc. did what geotavros sugested, and now i can debug fine! :)
Im still not clear thoug if this is a bug on QtCreator, or somehow my computer not having the windows debuger (seems unlikely since i have visual studio professional (including Visual C++) installed.
And another thing, is this related to the warning i get when i build using the vc compiler, as i explained here:
http://developer.qt.nokia.com/forums/viewthread/13925/
[/quote]
You should not do cross-postings to attract people to your issue. There is no need to.

Benzin

[quote author="koahnig" date="1327932180"]
You should not do cross-postings to attract people to your issue. There is no need to.
[/quote]
Hello, i did not made that post to "attract people to mine", i mentioned that post as i tought it would have something to do with this issue (as that post mentions .pdb files). sorry if it seemed that way.
The reason for my post was only (as mentioned in it), to know if this debugger issue was caused by a Qt designer problem, or by a problem of my particular installation. :)

kkoehne

For MSVC, Qt Creator uses the standalone debugger Microsoft provides with the Debugging Tools for Windows. It can't use the Visual Studio one, because, well, it's only available in Visual Studio. Ideally the Qt SDK would automatically install these, but it can't AFAIK due to license issues.

That's btw also covered in the Help :) http://doc.qt.nokia.com/qtcreator-snapshot/creator-debugger-engines.html

Benzin

Hi kkoehne, thanks for your reply. i understand the issue now.
Debugging seems to "mostly" work fine after i installed the Debugging tools for windows, even thoug it seems unable to provide some variable data.
for example, if i try to see the status of some QLabel, there are a lot of members i cant see because it sais "<Memory access error>".

I will have to really test the debugging facilities "in practice", with real projects to see if it meets my needs. If it doesnt work like i need it to, i can allways install the MinGW version of Qt along with MinGw compiler and GDB, and use that for developing, and only switch to the VC2008 compiler for the release builds.
¿Does the GCC debugger work better that the CDB? ¿Do you advice i use GCC instead?
thanks for your help

kkoehne

Hi Benzin, I don't know about the 'Memory Access Error' you're describing, please file a bug at bugreports.qt-project.org, or post to the qt-creator mailing list. I personally stopped using MinGW mostly because of it's crappy compiler it once had (might have been improved though in the last versions though). But then again Windows isn't my main development platform :) Anyhow, both MINGW and MSVC is fully supported by Qt Creator.

Guillaume

I have just downloaded and installed SDk 1.2 as an upgrade. And my project who used to work before now refuses to debug with the same message :

None of the debugger engines ‘Cdb engine, Gdb engine’ capable of debugging binaries of the type ‘x86-windows-msys-pe-32bit’ is configured correctly.

I am on Windows 7 x64 and trying to debug a simulator application using gcce toolchain. I confirm that gdb is present on the correct directory.

Any ideas ? Thanks

kkoehne

Guillaume, 'gcce toolchain' is AFAIK for embedded only ... Anyhow, just check that your toolchain is properly configured:

Check which toolchain is configured for your project under Projects, Build
(for the Simulator, it should probably be "MinGW as a GCC for Windows targets")
Click on "Manage..." for the toolchain. Check that the debugger path is properly configured
(It says C:\QtSDK\pythongdb\python_2.7based\gdb-i686-pc-mingw32.exe for me)

Guillaume

Toolchain was missing correct debugger path. The field was blank. I wonder why it was set alike.

Thanks, it now works

Uranium-235

I don't know if this is worthwhile to anyone but I put it together for myself to address the problem as I had it, obviously with some help from here but either I wasn't thorough in reading or I needed additional steps.

 Installing

Install QT SDK (it’s a 1.7 gigabyte install).
a. The USB Network Driver component failed on my install.
Install Debugging Tools for Windows SDK to have a debugger for stepping into code.

 Debugging a Project

Select Tools/Options to display the Options dialog.
Select Build & Run/Tool Chains.
Select the desired compiler from the list of Auto-detected.
Press the Clone button.
Select the Clone of … entry which was just created.
Press the Browse button.
Locate Microsoft’s Console Debugger:
(C:\Program Files\Windows Kits\8.0\Debuggers\x86\cdb.exe.)

The desired compiler entry was cloned because its parameters are read only. The clone is available for modification.

BrawnyLad

Hello Everyone:

I am struggling to get debugging working, and I feel quite "in the dark" about its setup.

I had the errors that began this thread. I tried everything in this thread and finally made progress by following Uranium-235's checklist.

I don't understand cloning, but at least I was able to run the debugger without errors. However, all of my breakpoints are ignored!

There is much that I don't understand about Tools->Options->Debugger:

Do I need to add something to the Source Path, or the Target Path, in the General sheet?
In these sheets, what does it mean that there are a bunch of items in a list? Are they all accessed, or do I have to specify the use of one, somehow?
In the CDB sheet, I added the CDB location folder in Source paths. Should I add something to Symbols paths? There are three paths specified currently, I don't know why.
There are many items listed in Options->Build & Run-> Tool Chains, (including the clone I made). Is it no problem to have so many items? Should I somehow indicate a priority?

Background: I inherited a large Qt project. It was created on a different computer; I downloaded Qt 4.8.1 for Desktop - MSVC2010 (Qt SKD).

Thanks!