CODEWITHSUNDEEP
qtvisual-c++debugging
WolfgangP
WolfgangP

Reputation: 3233

How can I make MSVC debugger step into Qt library source code again?

Until now my Visual Studio 2008 debugger gracefully stepped into Qt library code when I pressed F11. After upgrading Qt to the latest version and changing QTDIR, F11 does not step into library code anymore. Any clues how to make the debugger smart again?

Upvotes: 7

Views: 9113

Answers (2)

pixelgrease
pixelgrease

Reputation: 2118

@0xbaadf00d's recommendation to "open the Debug/Windows/Modules view" for verifying which modules have loaded successfully and which are not loaded is extremely useful.

Here is a summary of what I check when I need to step into Qt source code:

  • The DLLs must be for the Qt version in developer's Qt kit
  • The Qt .pdb files must be present in Qt kit's folders: bin, lib, plugins/platforms, plugins/qmltooling
  • Visual Studio Tools/Option/Debugging/Symbols needs paths to .pdb files: Screenshot of Visual Studio's Options/Debugging/Symbols settings for loading PDBs
  • If qt.conf file is used, must point to correct bin folder
  • If target is WinCE or WEC2013 and using HKLM\Loader\SystemPath, you must specify path to DLLs in SystemPath variable
  • Set the location for the source files in the project property pages: Screenshot of project configuration's "VC++ Directories" settings for "Source Directories"

Upvotes: 1

0xbaadf00d
0xbaadf00d

Reputation: 2643

Activate the modules list, Debug - Windows - Modules, to see what libraries are loaded and if debug symbols are loaded for those libraries. Note that you need to have the debugger active on your process to be able to do this.

In debug mode, the Qt libraries should be suffixed by d. QtCored4.dll for instance. If you see QtCore4.dll on the list, you have linked to the wrong libraries. If it does say QtCored4.dll but under Symbol Status there is something different than Symbols loaded., then that's the reason. You can manually load the symbols here by right clicking on the dll and selecting Load Symbols. It asks for the Pdb file after clicking that.

You can add more pdb file locations, if they weren't loaded but exist, from Tools - Options - Debugging(tree) - Symbols(tree). If you want the symbols to be automatically loaded.

Should it give some error, that the pdb file doesn't match the binary or something like that, you should re-build your Qt debug version, unless you have more pdb files to try. Use the Visual studio command prompt and go to the Qt directory, run configure and nmake. It takes a while, possibly some hours. There was some switch to only build debug version but i forgot where it goes. Note that the build might fail and after that it's a lot of fun www.google.com searches. The best bet might be to get the source only package, I forgot where to get that and it's not easily found. If you know where to get it, tell me please. I vaguely remember that there might be some other way to build the debug version, but this is the only one i know for sure.

Upvotes: 15

Related Questions