Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Debugger Not showing attribute values
Forum Updated to NodeBB v4.3 + New Features

Debugger Not showing attribute values

Scheduled Pinned Locked Moved Solved General and Desktop
7 Posts 3 Posters 2.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    leinad
    wrote on 2 Dec 2020, 15:18 last edited by
    #1

    Hi,

    I'm using Qt 5.15 with QtCreator and up to date with the latest patches in QtCreator. Compiling on Windows using VS 16.6.30204.135(amd64) and the debugger is configured auto-detected using cdb.exe located in c:\Program files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe.

    The problem is when I enter a function by single step the right panel that shows the current status of the values is blank, however when I go into some other function it then reappears and I'm able to see the variables and its values/contents. Also when I mouse hover over a variable there is nothing there and I get a tool tip "Expression to Complex" . It seems this broke some time ago when QTcreator notified me for an update which I went ahead and did. There have been several updates to QTCreator for the debugger since then but still I'm running into the same issue. It is frustrating because I can't see the sate of values just when I need them. I prefer not to place print statements all over the place which defeats the whole purpose of having a debugger in the first place.

    Is there some setting that needs to be implemented to fix this?

    Thanks in advance!

    1 Reply Last reply
    0
    • L Offline
      L Offline
      leinad
      wrote on 3 Dec 2020, 16:28 last edited by
      #2

      Any help please? Someone must know something?

      A 1 Reply Last reply 3 Dec 2020, 17:57
      0
      • L leinad
        3 Dec 2020, 16:28

        Any help please? Someone must know something?

        A Offline
        A Offline
        aha_1980
        Lifetime Qt Champion
        wrote on 3 Dec 2020, 17:57 last edited by aha_1980 12 Mar 2020, 17:58
        #3

        Hi @leinad,

        Please have a look into View > Views > Debugger Log and search for obvious errors.

        Regards

        Qt has to stay free or it will die.

        1 Reply Last reply
        0
        • L Offline
          L Offline
          leinad
          wrote on 8 Dec 2020, 13:59 last edited by
          #4

          Hi aha_1980,

          I did as you said but did not see any obvious errors at least no messages which are different from when it does work. I did find something out accidently which is strange. When I inserted qDebug() statements in the method, then the debugger showed the attribute values in the left pane. So it seems adding new code cleared it up. Any ideas why that would happen?

          Thanks again!

          J 1 Reply Last reply 8 Dec 2020, 14:19
          0
          • L leinad
            8 Dec 2020, 13:59

            Hi aha_1980,

            I did as you said but did not see any obvious errors at least no messages which are different from when it does work. I did find something out accidently which is strange. When I inserted qDebug() statements in the method, then the debugger showed the attribute values in the left pane. So it seems adding new code cleared it up. Any ideas why that would happen?

            Thanks again!

            J Offline
            J Offline
            JonB
            wrote on 8 Dec 2020, 14:19 last edited by
            #5

            @leinad
            Did you completely clean the output directory and rebuild when you noticed the problem originally? If you remove the qDebug() statements now (and rebuild) so that it is back as it was when you found it wrong, does it revert to wrong or stay good?

            1 Reply Last reply
            1
            • L Offline
              L Offline
              leinad
              wrote on 8 Dec 2020, 15:54 last edited by
              #6

              I always did a new clean build. I removed the debug statements and it continues to display. So for some reason adding a statement and then later removing it, clears it up. I always do "Clean Project xxx for all Configurations". Should there be something else I should do?

              Also which may or may not be related, when I hover on a variable and get a value with a tool tip, when I click on the pin, the tooltip should stay up so as the variable changes I should see it in the tool tip. What happens is when clicking on the pin the tool tip disappears and the variable is highlighted in the right debug panel. The tool tip used to always stay up until I dismissed it. I think that changed on a debugger update within QTCreator.

              J 1 Reply Last reply 8 Dec 2020, 18:32
              0
              • L leinad
                8 Dec 2020, 15:54

                I always did a new clean build. I removed the debug statements and it continues to display. So for some reason adding a statement and then later removing it, clears it up. I always do "Clean Project xxx for all Configurations". Should there be something else I should do?

                Also which may or may not be related, when I hover on a variable and get a value with a tool tip, when I click on the pin, the tooltip should stay up so as the variable changes I should see it in the tool tip. What happens is when clicking on the pin the tool tip disappears and the variable is highlighted in the right debug panel. The tool tip used to always stay up until I dismissed it. I think that changed on a debugger update within QTCreator.

                J Offline
                J Offline
                JonB
                wrote on 8 Dec 2020, 18:32 last edited by
                #7

                @leinad said in Debugger Not showing attribute values:

                So for some reason adding a statement and then later removing it, clears it up.

                Since you know that in itself cannot change anything, don't you think it does indicate there was some build artefact left around? I don't know what Clean Project ... actually does, I just delete all the files in the build directory. Anyway it's solved now.

                1 Reply Last reply
                1

                4/7

                8 Dec 2020, 13:59

                • Login

                • Login or register to search.
                4 out of 7
                • First post
                  4/7
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved