How to solve Qt Creators variable-"<not accessible>" behavior?

20,479

Solution 1

Unfortunately it's only a workaround (but I will write more as soon as possible) but this post pointed me to just disable "Load system GDB pretty printers" in Tools->Options->Debugger->GDB

This behavior is a filed bug in QtCreator 3.0

seems to work for me now!

EDIT: Although the bug tracker for QtCreator 3.0 says the bug has been fixed, the bug actually persists in later versions - at least as of v3.1.2 . Fortunately the same suggested workaround applies.

Solution 2

For windows users updated to Qt 5.11.2 and who using CDB.

On installer (Qt Maintenance tool) make sure the 'Qt -> Qt 5.11.2 -> Qt Debug Information Files' is checked. (There was no such option in previous releases).

Share:
20,479
frans
Author by

frans

Updated on November 12, 2020

Comments

  • frans
    frans over 3 years

    I have the same problem as described in Variables in Locals and Expressions not accessible in QT Creator but I want to find a way how to "repair" Qt Creator showing default composite types like std::string in the debugging window again.

    I've updated from Creator 2.8 to 3.0 via a dist upgrade (fedora 18=>20) and I know things can go wrong there but I really want to avoid re-installing the whole OS just for Qt Creator.

    Is there any way to make the Creator more verbose or does it write to a log file?

    Is Qt Creator 3.0 known to show nice values for composite types anyway?

    What components can I check and how?