Debugger for Windows Binaries

[AndrewDavis]

Hello,

I'm fairly new to C++ and QtCreator. I want to debug my program, but I think this error I'm receiving is preventing me from doing that (the breakpoints aren't working at all):

"http://www.gilgil.net/communities/11554":http://www.gilgil.net/communities/11554

although the error I got was "msvc2010", not "msvc2008". Anyways, I tried installing the "Debugging Tools for Windows as a Standalone Component" from here:

"http://msdn.microsoft.com/en-US/windows/hardware/gg463009/":http://msdn.microsoft.com/en-US/windows/hardware/gg463009/

but now I don't know what else to do. I restarted QtCreator and I still receive the error. I think there's something I have to do in the Tools > Options > Build & Run and Tools > Options > Debugger options, but I have no idea what to do there. I'm on Windows 8, using QtCreator 2.4.1 and trying to run a simple Qt Dialog application. If you could help me out, that would be great.

Also, if this isn't the reason that my breakpoints aren't working, then how do I fix that problem, and how do I disable this debugger error I'm getting if I don't need to fix it as I was told to above?

Thank you,

• Andrew

[tucnak]

AFAIK, gdb.exe is built-in part or MinGW compiler. It must be located in ....\mingw\bin.

Example if you are working in MinGW enviropment:
@
cd C:\Users<username>\Programs\MyProgram
gdb myprogram.exe
@

Or you can set it from Qt Creator.

[tobias.hunger]

Just ignore tucnak... gdb most likely does not even apply to your problem.

So which Qt version are you using to build your project with? Check the Projects mode (bar on the left side), it should show the Qt version used. Which ABI is it using? Click on "Manage" and find the Qt version you are using in the dialog that will open and hover it to get the tool tip. Is the ABI mentioning "msvcSOMEVERSION" somewhere?

If it does then you will indeed need cdb for debugging. If it says "mingw" then you will need gdb instead. Sorry, but C++ development on windows is a real mess. No idea what Microsoft is thinking.

Once you are sure which debugger you actually need, please make sure that it is available. Prefer the gdb that we ship with Qt Creator to the one from mingw if you have any... ours is known to work, which we can unfortunately not claim for others.

If you can start debugging an application even in spite of the messages and it is just breakpoints that are not hit: Did you build in debug mode? Release mode does not have the information needed to place breakpoints based on lines.

[AndrewDavis]

Thanks for your help, but I've decided that I will just use plain C++ in Visual Studio for my project. Qt is causing more problems (like this one) than it is helping me with, so I don't see the point of dealing with someone else's mess. I'm sure your response will help other people who have had similar problems to mine in the future though.

Thanks anyways,

• Andrew

[tucnak]

[quote author="Tobias Hunger" date="1340738780"]Just ignore tucnak... gdb most likely does not even apply to your problem.

So which Qt version are you using to build your project with? Check the Projects mode (bar on the left side), it should show the Qt version used. Which ABI is it using? Click on "Manage" and find the Qt version you are using in the dialog that will open and hover it to get the tool tip. Is the ABI mentioning "msvcSOMEVERSION" somewhere?

If it does then you will indeed need cdb for debugging. If it says "mingw" then you will need gdb instead. Sorry, but C++ development on windows is a real mess. No idea what Microsoft is thinking.

Once you are sure which debugger you actually need, please make sure that it is available. Prefer the gdb that we ship with Qt Creator to the one from mingw if you have any... ours is known to work, which we can unfortunately not claim for others.

If you can start debugging an application even in spite of the messages and it is just breakpoints that are not hit: Did you build in debug mode? Release mode does not have the information needed to place breakpoints based on lines.[/quote]

Sorry for wrong comment. I've thought that here was another problem. Now, I will read full thread before posting.