Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Qt 6.6.1 While debugging local variables <Value unavailable error> occurs

Qt 6.6.1 While debugging local variables <Value unavailable error> occurs

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
9 Posts 3 Posters 691 Views
  • 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.
  • W Offline
    W Offline
    weti59
    wrote on last edited by
    #1

    After update from Qt 5.15.0 to Qt 6.6.1 the values of local Qt objects there are not shown.

    Configuration:
    Windows 10
    QT Creator 12.0 from 2023-11-22
    Qt 6.6.1 from 2023-11-21
    Qt 5.15.0 from 2020-05-15

    Using the following build (Qt 6.6.1 with 64bit):

    228ffe57-4a22-4fe9-9562-3765f76300f4-grafik.png

    the debugger shows no content of QString object "test", instead <Value unavailable error> occurs:

    7a6c43a6-e1d4-4e4f-be98-771259870c73-grafik.png

    When using old build (Qt 5.15.0 with 32bit) with no changes in the configuration of QT Creator 12.0

    712a812b-7f9d-42d3-a0de-5d9e6d544306-grafik.png

    everything is fine:

    31d684bc-2c5a-45aa-9b80-355c17077685-grafik.png

    The Windows path includes both Qt Versions:

    31db6bfc-5e46-4f13-bf12-f844bd4476ee-grafik.png

    How to fix this problem?
    Thanks in Advanced!

    Pl45m4P 1 Reply Last reply
    0
    • Christian EhrlicherC Christian Ehrlicher moved this topic from General and Desktop on
    • W weti59

      @cristian-adam

      i've just installed Qt 6.5.3 but ther is no difference, the variables are not accessable...

      aa211d11-d571-46d1-af2a-3dfbc5f94409-grafik.png

      a1f91950-f361-4ed5-a396-cbc7236d3e73-grafik.png

      So it is not a problem within Qt but a problem within my installation.

      What else should i check ?

      cristian-adamC Online
      cristian-adamC Online
      cristian-adam
      wrote on last edited by
      #8

      In Settings -> Debugger -> CDB make sure you have the Python-Dumper verwenden checkbox enabled.

      The whole pretty printing of Qt Types is done via Python dumpers. I don't know how it works for Qt5, it shouldn't.

      W 1 Reply Last reply
      3
      • W weti59

        After update from Qt 5.15.0 to Qt 6.6.1 the values of local Qt objects there are not shown.

        Configuration:
        Windows 10
        QT Creator 12.0 from 2023-11-22
        Qt 6.6.1 from 2023-11-21
        Qt 5.15.0 from 2020-05-15

        Using the following build (Qt 6.6.1 with 64bit):

        228ffe57-4a22-4fe9-9562-3765f76300f4-grafik.png

        the debugger shows no content of QString object "test", instead <Value unavailable error> occurs:

        7a6c43a6-e1d4-4e4f-be98-771259870c73-grafik.png

        When using old build (Qt 5.15.0 with 32bit) with no changes in the configuration of QT Creator 12.0

        712a812b-7f9d-42d3-a0de-5d9e6d544306-grafik.png

        everything is fine:

        31d684bc-2c5a-45aa-9b80-355c17077685-grafik.png

        The Windows path includes both Qt Versions:

        31db6bfc-5e46-4f13-bf12-f844bd4476ee-grafik.png

        How to fix this problem?
        Thanks in Advanced!

        Pl45m4P Offline
        Pl45m4P Offline
        Pl45m4
        wrote on last edited by
        #2

        @weti59

        Do you have both of your Qt versions added as source to your debugger?
        Check Settings -> Debugger tab


        If debugging is the process of removing software bugs, then programming must be the process of putting them in.

        ~E. W. Dijkstra

        1 Reply Last reply
        1
        • W Offline
          W Offline
          weti59
          wrote on last edited by
          #3

          Hi Pl45m4,

          I have none of the Qt Versions added in Settings->debugger.

          57f4b96c-b689-4105-adf2-8244fcd41553-grafik.png

          is empty,

          and

          e487af00-3c8a-4342-bb13-f1e3e350722a-grafik.png

          is empty

          and

          9df010be-e70f-4565-a3d0-c3b7c2fd33e3-grafik.png

          is empty too...

          So what shall i do ?

          cristian-adamC 1 Reply Last reply
          0
          • W weti59

            Hi Pl45m4,

            I have none of the Qt Versions added in Settings->debugger.

            57f4b96c-b689-4105-adf2-8244fcd41553-grafik.png

            is empty,

            and

            e487af00-3c8a-4342-bb13-f1e3e350722a-grafik.png

            is empty

            and

            9df010be-e70f-4565-a3d0-c3b7c2fd33e3-grafik.png

            is empty too...

            So what shall i do ?

            cristian-adamC Online
            cristian-adamC Online
            cristian-adam
            wrote on last edited by
            #4

            Make sure that you have installed the Qt Debug Information Files for your Qt installation.

            alt text

            W 1 Reply Last reply
            1
            • cristian-adamC cristian-adam

              Make sure that you have installed the Qt Debug Information Files for your Qt installation.

              alt text

              W Offline
              W Offline
              weti59
              wrote on last edited by
              #5

              @cristian-adam

              Thank you for your suggestion, but
              i've already checked the installation...

              8bcc6051-f4d3-4192-bea0-dd7a6ac69f6e-grafik.png

              QT Creator 12.0.0 is installed with "debugging tools" and "debug symbols"

              1343ec04-26d8-4573-8701-4bf3cab181b0-grafik.png

              QT 6.6.1 is installed with MSVC 2019 64 bit and "QT Debug information files"

              30a29efb-635d-4811-bc83-4f8b26dfc3cd-grafik.png

              QT 5.15.0 is installed with MSVC 2019 32 bit and 64 bit and "QT Debug information files"

              So when i look into the ..\QT\6.6.1\msvc2019_64\bin directory there are *.pdb files for all dlls.

              83353fb9-d015-4151-b2c9-f37f57e4dc2f-grafik.png

              Similar to the ...\QT\5.15.0\msvc2019\bin directory

              efba5e85-8b31-4964-8e6b-18781c1d7b0c-grafik.png

              I still have no explanation for this behavior...

              cristian-adamC 1 Reply Last reply
              0
              • W weti59

                @cristian-adam

                Thank you for your suggestion, but
                i've already checked the installation...

                8bcc6051-f4d3-4192-bea0-dd7a6ac69f6e-grafik.png

                QT Creator 12.0.0 is installed with "debugging tools" and "debug symbols"

                1343ec04-26d8-4573-8701-4bf3cab181b0-grafik.png

                QT 6.6.1 is installed with MSVC 2019 64 bit and "QT Debug information files"

                30a29efb-635d-4811-bc83-4f8b26dfc3cd-grafik.png

                QT 5.15.0 is installed with MSVC 2019 32 bit and 64 bit and "QT Debug information files"

                So when i look into the ..\QT\6.6.1\msvc2019_64\bin directory there are *.pdb files for all dlls.

                83353fb9-d015-4151-b2c9-f37f57e4dc2f-grafik.png

                Similar to the ...\QT\5.15.0\msvc2019\bin directory

                efba5e85-8b31-4964-8e6b-18781c1d7b0c-grafik.png

                I still have no explanation for this behavior...

                cristian-adamC Online
                cristian-adamC Online
                cristian-adam
                wrote on last edited by
                #6

                It might be that Qt 6.6.1 is too new, and introduced a change that is not handled by Qt Creator 12.0.0.

                What happens is you use Qt 6.5.x or 6.6.0? If these versions work fine please do create a bug report at https://bugreports.qt.io/secure/CreateIssue.jspa?pid=10512

                W 1 Reply Last reply
                0
                • cristian-adamC cristian-adam

                  It might be that Qt 6.6.1 is too new, and introduced a change that is not handled by Qt Creator 12.0.0.

                  What happens is you use Qt 6.5.x or 6.6.0? If these versions work fine please do create a bug report at https://bugreports.qt.io/secure/CreateIssue.jspa?pid=10512

                  W Offline
                  W Offline
                  weti59
                  wrote on last edited by
                  #7

                  @cristian-adam

                  i've just installed Qt 6.5.3 but ther is no difference, the variables are not accessable...

                  aa211d11-d571-46d1-af2a-3dfbc5f94409-grafik.png

                  a1f91950-f361-4ed5-a396-cbc7236d3e73-grafik.png

                  So it is not a problem within Qt but a problem within my installation.

                  What else should i check ?

                  cristian-adamC 1 Reply Last reply
                  0
                  • W weti59

                    @cristian-adam

                    i've just installed Qt 6.5.3 but ther is no difference, the variables are not accessable...

                    aa211d11-d571-46d1-af2a-3dfbc5f94409-grafik.png

                    a1f91950-f361-4ed5-a396-cbc7236d3e73-grafik.png

                    So it is not a problem within Qt but a problem within my installation.

                    What else should i check ?

                    cristian-adamC Online
                    cristian-adamC Online
                    cristian-adam
                    wrote on last edited by
                    #8

                    In Settings -> Debugger -> CDB make sure you have the Python-Dumper verwenden checkbox enabled.

                    The whole pretty printing of Qt Types is done via Python dumpers. I don't know how it works for Qt5, it shouldn't.

                    W 1 Reply Last reply
                    3
                    • cristian-adamC cristian-adam

                      In Settings -> Debugger -> CDB make sure you have the Python-Dumper verwenden checkbox enabled.

                      The whole pretty printing of Qt Types is done via Python dumpers. I don't know how it works for Qt5, it shouldn't.

                      W Offline
                      W Offline
                      weti59
                      wrote on last edited by
                      #9

                      @cristian-adam

                      This has done the trick !!

                      Python-Dumper was not checked and after i checked it, the contents of the variables where shown.

                      Thank you very much,
                      Problem is solved...

                      323860ee-c97f-4918-b5c9-ca2d27759c5d-grafik.png

                      It is not very obvious to check this option, how do you know about it ???

                      8c7fd0eb-cf75-409d-98b3-ebe5d33c56dc-grafik.png

                      1 Reply Last reply
                      1
                      • W weti59 has marked this topic as solved on

                      • Login

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