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. Debugger works only if I use Qt 5.15.9

Debugger works only if I use Qt 5.15.9

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
6 Posts 2 Posters 869 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.
  • ademmlerA Offline
    ademmlerA Offline
    ademmler
    wrote on last edited by
    #1

    hi folks,

    I experience that the debugger works only with Qt 5.15.9.
    When I try to use 5.15.10 or 5.15.11 the debugger does not function properly.
    This means it does not stop at breakpoints.

    Does somebody else have this issue?
    What could be the reason?

    Regards Alexander

    1 Reply Last reply
    0
    • ademmlerA Offline
      ademmlerA Offline
      ademmler
      wrote on last edited by
      #6

      I found out, that disabling all deployment steps makes the debugger to work properly.

      1 Reply Last reply
      0
      • andrA Offline
        andrA Offline
        andr
        wrote on last edited by
        #2

        Can you show the Debugger log (contents of right pane of Views->Views...->Debugger Log)?

        ademmlerA 1 Reply Last reply
        0
        • ademmlerA Offline
          ademmlerA Offline
          ademmler
          wrote on last edited by
          #3
          This post is deleted!
          1 Reply Last reply
          0
          • andrA andr

            Can you show the Debugger log (contents of right pane of Views->Views...->Debugger Log)?

            ademmlerA Offline
            ademmlerA Offline
            ademmler
            wrote on last edited by
            #4

            @andr

            Hi andr,

            I hope this is what you where asking for.

            >@
            >event={type="4",data="0x7fb61282a008 Event: broadcaster = 0x7fb60cab1c50 (lldb.process), type = 0x00000004 (stdout-available), data = { process = 0x7fb60cab1c18 (pid = 2884), state = running}",msg="None",flavor="Process::ProcessEventData",state="running",bp="No value"}@
            >@
            >output={channel="stdout",data="323032322D31322D30322030393A33393A32322E3131363432392B30313030205370656374726170726F6F66335B323838343A31383535385D2022476F74206D6F6E69746F722064657461696C733A205650323738352D324B2020220D0A323032322D31322D30322030393A33393A32322E3136303832342B30313030205370656374726170726F6F66335B323838343A31383535385D20224D6F6E69746F7220776869746520706F696E743A2058595A3D3132362E323735203133312E363039203132302E34333320436F6C6F7274656D70657261747572653D353434352E3737220D0A323032322D31322D30322030393A33393A32322E3136303939332B30313030205370656374726170726F6F66335B323838343A31383535385D2022557365206D6F6E69746F722070726F66696C653A202F55736572732F6164656D6D6C65722F4C6962726172792F436F6C6F7253796E632F50726F66696C65732F56535F4435355F31303131323032322E696363220D0A323032322D31322D30322030393A33393A32322E3136313134322B30313030205370656374726170726F6F66335B323838343A31383535385D2022476F74206261736963206D6F6E69746F7220696E666F726D6174696F6E2E220D0A323032322D31322D30322030393A33393A32322E3136313236332B30313030205370656374726170726F6F66335B323838343A31383535385D2022436865636B696E67206D6F6E69746F722064657461696C73206E6F772E220D0A"}@
             2022-12-02 09:39:22.116429+0100 Spectraproof3[2884:18558] "Got monitor details: VP2785-2K  "
             2022-12-02 09:39:22.160824+0100 Spectraproof3[2884:18558] "Monitor white point: XYZ=126.275 131.609 120.433 Colortemperature=5445.77"
             2022-12-02 09:39:22.160993+0100 Spectraproof3[2884:18558] "Use monitor profile: /Users/ademmler/Library/ColorSync/Profiles/VS_D55_10112022.icc"
             2022-12-02 09:39:22.161142+0100 Spectraproof3[2884:18558] "Got basic monitor information."
             2022-12-02 09:39:22.161263+0100 Spectraproof3[2884:18558] "Checking monitor details now."
            
            <36fetchDisassembler({"address":0,"flavor":"att","function":"","token":36})
            >(lldb) script theDumper.fetchDisassembler({"address":0,"flavor":"att","function":"","token":36})
            
            >@
            >result={token="36",lines=[]}@
            >36^
            
            <37fetchDisassembler({"address":0,"flavor":"att","function":"","token":37})
            >(lldb) script theDumper.fetchDisassembler({"address":0,"flavor":"att","function":"","token":37})
            
            >@
            >result={token="37",lines=[]}@
            >37^
            
            andrA 1 Reply Last reply
            0
            • ademmlerA ademmler

              @andr

              Hi andr,

              I hope this is what you where asking for.

              >@
              >event={type="4",data="0x7fb61282a008 Event: broadcaster = 0x7fb60cab1c50 (lldb.process), type = 0x00000004 (stdout-available), data = { process = 0x7fb60cab1c18 (pid = 2884), state = running}",msg="None",flavor="Process::ProcessEventData",state="running",bp="No value"}@
              >@
              >output={channel="stdout",data="323032322D31322D30322030393A33393A32322E3131363432392B30313030205370656374726170726F6F66335B323838343A31383535385D2022476F74206D6F6E69746F722064657461696C733A205650323738352D324B2020220D0A323032322D31322D30322030393A33393A32322E3136303832342B30313030205370656374726170726F6F66335B323838343A31383535385D20224D6F6E69746F7220776869746520706F696E743A2058595A3D3132362E323735203133312E363039203132302E34333320436F6C6F7274656D70657261747572653D353434352E3737220D0A323032322D31322D30322030393A33393A32322E3136303939332B30313030205370656374726170726F6F66335B323838343A31383535385D2022557365206D6F6E69746F722070726F66696C653A202F55736572732F6164656D6D6C65722F4C6962726172792F436F6C6F7253796E632F50726F66696C65732F56535F4435355F31303131323032322E696363220D0A323032322D31322D30322030393A33393A32322E3136313134322B30313030205370656374726170726F6F66335B323838343A31383535385D2022476F74206261736963206D6F6E69746F7220696E666F726D6174696F6E2E220D0A323032322D31322D30322030393A33393A32322E3136313236332B30313030205370656374726170726F6F66335B323838343A31383535385D2022436865636B696E67206D6F6E69746F722064657461696C73206E6F772E220D0A"}@
               2022-12-02 09:39:22.116429+0100 Spectraproof3[2884:18558] "Got monitor details: VP2785-2K  "
               2022-12-02 09:39:22.160824+0100 Spectraproof3[2884:18558] "Monitor white point: XYZ=126.275 131.609 120.433 Colortemperature=5445.77"
               2022-12-02 09:39:22.160993+0100 Spectraproof3[2884:18558] "Use monitor profile: /Users/ademmler/Library/ColorSync/Profiles/VS_D55_10112022.icc"
               2022-12-02 09:39:22.161142+0100 Spectraproof3[2884:18558] "Got basic monitor information."
               2022-12-02 09:39:22.161263+0100 Spectraproof3[2884:18558] "Checking monitor details now."
              
              <36fetchDisassembler({"address":0,"flavor":"att","function":"","token":36})
              >(lldb) script theDumper.fetchDisassembler({"address":0,"flavor":"att","function":"","token":36})
              
              >@
              >result={token="36",lines=[]}@
              >36^
              
              <37fetchDisassembler({"address":0,"flavor":"att","function":"","token":37})
              >(lldb) script theDumper.fetchDisassembler({"address":0,"flavor":"att","function":"","token":37})
              
              >@
              >result={token="37",lines=[]}@
              >37^
              
              andrA Offline
              andrA Offline
              andr
              wrote on last edited by
              #5

              @ademmler , yes that's what I meant, but preferably a somewhat more complete version of it.

              1 Reply Last reply
              0
              • ademmlerA Offline
                ademmlerA Offline
                ademmler
                wrote on last edited by
                #6

                I found out, that disabling all deployment steps makes the debugger to work properly.

                1 Reply Last reply
                0
                • ademmlerA ademmler 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