Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

QString not accessible in QtCreator Debug



  • Re: QtCreator no longer shows Qstring values in debug...

    So I can't see the values of strings in QtCreator when debugging on Windows. I've tracked this down to only being a problem in Qt6.0, Qt5.15 works fine. Something to do with Qt hooks according to the debugging log. What do I need to poke to fix it for 6.0 ?


    Type information missing error for qtHookData




    *** 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: Qt5Cored!qtHookData ***



    Type information missing error for qtHookData




    *** 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: Qt5Cored!qtHookData ***



    Type information missing error for qtHookData
    .call Qt5Cored!qVersion()
    ^ Symbol not a function in '.call Qt5Cored!qVersion()'
    DEBUG: Failed to call function 'Qt5Cored!qVersion()' error: Execute failed: E_FAIL Unknown error 517
    result={data=[{iname="local.argc",name="argc",address="0x31decffd80",numchild="0",type="int",value="1"},{iname="local.argv",name="argv",numchild="1",type="char **",valueencoded="itemcount",value="1"},{iname="local.andy",name="andy",numchild="0",type="QString",valueencoded="notaccessible",value=""},{iname="local.app",name="app",address="0x31decffd38",numchild="1",type="QGuiApplication",value=""},{iname="local.engine",name="engine",address="0x31decffd48",numchild="1",type="QQmlApplicationEngine",value=""},{iname="local.url",name="url",numchild="0",type="QUrl",valueencoded="notaccessible",value=""}],partial="0",timings=[]}
    <Rebuild Watchmodel 4 @ 11:09:29.369 [65510ms] >
    Finished retrieving data.



  • Updated from Qt 6.0.0 to Qt 6.0.1 and this has gone away.


Log in to reply