Qt Creator unable to find any symbols of current project
-
I'm trying to debug code in Creator, but it fails to find/load/(other?) symbols of the current, compiled project (stored in a .pdb file in the same output folder as the .exe file, as per default). After failing to find the symbols of the current project it won't display any variables, even simple types.
My Setup is default install og Qt 6.02, fresh install of MSVC 2022, most recent Windows 10, cmake 3.22, and loading the project through the CMakeLists.txt. All the compiler kits/toolchain is the default Qt Creator detects, the only thing modified from default is the name of the output folder.
This is not the first time I've encountered this problem, but I've assumed there was some env setup that caused it, but this is as stock&default as it gets, and I assume Qt Creator usually can display local variables, so this seems like a bug. Or is there some setup needed to make CDB work?
The message in the debug console is this:
************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: xxx_d!Xxxx::XxxXxxx *** *** *** ************************************************************************* -
I'm trying to debug code in Creator, but it fails to find/load/(other?) symbols of the current, compiled project (stored in a .pdb file in the same output folder as the .exe file, as per default). After failing to find the symbols of the current project it won't display any variables, even simple types.
My Setup is default install og Qt 6.02, fresh install of MSVC 2022, most recent Windows 10, cmake 3.22, and loading the project through the CMakeLists.txt. All the compiler kits/toolchain is the default Qt Creator detects, the only thing modified from default is the name of the output folder.
This is not the first time I've encountered this problem, but I've assumed there was some env setup that caused it, but this is as stock&default as it gets, and I assume Qt Creator usually can display local variables, so this seems like a bug. Or is there some setup needed to make CDB work?
The message in the debug console is this:
************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: xxx_d!Xxxx::XxxXxxx *** *** *** *************************************************************************Newermind, this is https://bugreports.qt.io/browse/QTCREATORBUG-25192 that hasn't been fixed. QtCreator doesn't work with /DEBUG:FASTLINK (or more specifically the Python Dumper), and the bugfix is simply "don't do that".