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

Problem with qtcreator debugger. Cannot see info about 'this' pointer in own code.



  • I am using qtcreator 4.6.2 and Qt 5.11.1
    When I enter in debug modus into one of my own classes, the debugger of local vars does not show any information about the *this class.

    I am no newbie, but at this point I don't know what else to do.
    Has anybody a similar observation, or even better a solution for the problem?



  • @F.Haferkorn

    What is your OS and toolchain?


  • Lifetime Qt Champion

    Hi @F.Haferkorn,

    please have a look in the debugger log (Windows > Views > Debugger Log) if there is anything obvious.

    And as @koahnig said, which compiler/debugger are your using under which OS?



  • @aha_1980 Wow!
    I've been using Qt for 5 years now and somehow have never used the debugger log.
    That looks incredibly useful. Thanks for mentioning it.



  • Hello,
    I am usig Visual Studio 2015 64 bit under Windows 10.
    The Debugger is "Windows 10 x64".



  • Wen I try to access the "this" pointer of the Class FhpPosMix e.g in the Constructor, The left pane of the debuger Console shows this text near at the end of;
    result={data=[{iname="local.this",name="this",origaddr="0xc68c37ef70",address="0x291c0dbe578",address="0x291c0dbe578",numchild="1",type="fhs::FhspPosMix",value=""},{iname="watch.0",wname="6D5F706F736974696F6E",origaddr="0x291c0dbe5a8",address="0x291c0db9630",address="0x291c0db9630",numchild="1",type="fhs::FhspMoveSpherical",value=""}],partial="0",timings=[]}
    <Rebuild Watchmodel 136 @ 11:44:41.619 [134725ms] >
    sAlle Daten erhalten

    <!qtcreatorcdbext.script theDumper.fetchVariables({"autoderef":1,"context":"","displaystringlimit":"100","dyntype":1,"expanded":["local","local.this","return","watch","inspect"],"fancy":1,"formats":{},"nativemixed":0,"partialvar":"local.this","passexceptions":0,"qobjectnames":1,"stringcutoff":"10000","typeformats":{},"uninitialized":[],"watchers":[{"exp":"6d5f706f736974696f6e","iname":"watch.0"}]})

    result={data=[{iname="local.this",name="this",origaddr="0xc68c37ef70",address="0x291c0dbe578",address="0x291c0dbe578",numchild="1",sortable="1",children=[],type="fhs::FhspPosMix",value=""},{iname="watch.0",wname="6D5F706F736974696F6E",origaddr="0x291c0dbe5a8",address="0x291c0db9630",address="0x291c0db9630",numchild="1",type="fhs::FhspMoveSpherical",value=""}],partial="1",timings=[]}
    <Rebuild Watchmodel 137 @ 11:44:48.809 [7190ms] >
    sAlle Daten erhalten
    dADJUSTING CHILD EXPECTATION FOR local.this

    <!qtcreatorcdbext.modules
    <!qtcreatorcdbext.modules
    <!qtcreatorcdbext.modules

    I have no clue at all, what the problem is...



  • The right pane of the debugger-log indicates:

    result={data=[{iname="local.this",name="this",origaddr="0xc68c37ef70",address="0x291c0dbe578",address="0x291c0dbe578",numchild="1",sortable="1",children=[],type="fhs::FhspPosMix",value=""},{iname="watch.0",wname="6D5F706F736974696F6E",origaddr="0x291c0dbe5a8",address="0x291c0db9630",address="0x291c0db9630",numchild="1",type="fhs::FhspMoveSpherical",value=""}],partial="1",timings=[]}
    <Rebuild Watchmodel 137 @ 11:44:48.809 [7190ms] >
    sAlle Daten erhalten
    dADJUSTING CHILD EXPECTATION FOR local.this
    <!qtcreatorcdbext.modules

    The reason for this misbehaviour might be:
    I modified some of the default settings of the debugger.
    Strange, but at other code-positions, accessing this pointer (in debugger) works flawless.



  • @F.Haferkorn

    When you can produce a small project showing the effect, you may want to check on JIRA for a bug report or file one yourself.


  • Lifetime Qt Champion

    Hi @F.Haferkorn,

    I remember that some users here had problems with the Python dumpers (or pretty printers) and disabling them in the Options helped.

    Otherwise you can create a report wiht minimal example and debugger log attached, as @koahnig already said.

    Regards



  • Thanks @koahnig and @aha_1980.
    I will setup a smaller Project an then do the recommended steps.
    Regards...