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. QT opens disassembler when debugging
Forum Updated to NodeBB v4.3 + New Features

QT opens disassembler when debugging

Scheduled Pinned Locked Moved Solved General and Desktop
17 Posts 7 Posters 8.2k 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.
  • aha_1980A aha_1980

    @Nocksen said in QT opens disassembler when debugging:

    I dont see anythin important in the logs

    Can you show it?

    D Offline
    D Offline
    deleted581
    wrote on last edited by
    #7

    @aha_1980 https://pastebin.com/if6hdZn6

    aha_1980A 1 Reply Last reply
    0
    • D deleted581

      @aha_1980 https://pastebin.com/if6hdZn6

      aha_1980A Offline
      aha_1980A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on last edited by
      #8

      @Nocksen

      /home/.../Schreibtisch/C++/1.Programmierung mit C++/Kapitel 5/3.Übungen 1-14/build-Uebung3-Desktop_Qt_5_11_1_GCC_64bit-Debug/Uebung3

      Try using a project (and build) directory without spaces and without Umlauts (only ASCII characters).

      I'm pretty sure that's the reason.

      Regards

      Qt has to stay free or it will die.

      1 Reply Last reply
      3
      • D Offline
        D Offline
        deleted581
        wrote on last edited by
        #9

        @aha_1980 Thanks, that was the problem :)

        Pablo J. RoginaP 1 Reply Last reply
        1
        • D deleted581

          @aha_1980 Thanks, that was the problem :)

          Pablo J. RoginaP Offline
          Pablo J. RoginaP Offline
          Pablo J. Rogina
          wrote on last edited by
          #10

          @Nocksen if your issue is solved please don't forget to mark your post as such. Thanks

          Upvote the answer(s) that helped you solve the issue
          Use "Topic Tools" button to mark your post as Solved
          Add screenshots via postimage.org
          Don't ask support requests via chat/PM. Please use the forum so others can benefit from the solution in the future

          1 Reply Last reply
          2
          • aha_1980A Offline
            aha_1980A Offline
            aha_1980
            Lifetime Qt Champion
            wrote on last edited by
            #11

            FYI: I created https://bugreports.qt.io/browse/QTCREATORBUG-20834 to get a warning message for such cases.

            Qt has to stay free or it will die.

            1 Reply Last reply
            1
            • N Offline
              N Offline
              Neotod
              wrote on last edited by
              #12

              @aha_1980 I try all things you have said, making directory without spaces.
              but still I have that problem with my debugger.

              aha_1980A 1 Reply Last reply
              0
              • N Neotod

                @aha_1980 I try all things you have said, making directory without spaces.
                but still I have that problem with my debugger.

                aha_1980A Offline
                aha_1980A Offline
                aha_1980
                Lifetime Qt Champion
                wrote on last edited by
                #13

                Hi @Neotod,

                then please show the debugger log (Windows > Views).

                Also provide the needed information about operating system, Qt and Creator version, used compiler, 32 or 64 bit.

                Have you tried a minimal example?

                Regards

                Qt has to stay free or it will die.

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  Mehdi Karimi
                  wrote on last edited by Mehdi Karimi
                  #14

                  Hi,

                  I installed Ubuntu 20.04 today. Then I installed Qt 5.15.2. I have the disassembler issue. Then I removed whole Qt and install a fresh Qt6. The issue is still there. I do not use space or any special character in my build directory. I have the same issue like https://imgur.com/a/aUf0354

                  compiler: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
                  Debuger: GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2

                  It always shows disassembler when debuger reaches std::async(std::lunch::async,....) function!!!(But maybe unrelataed).

                  Even I upgrade gcc to 10. The problem still is there.

                  1 Reply Last reply
                  0
                  • PsnarfP Offline
                    PsnarfP Offline
                    Psnarf
                    wrote on last edited by
                    #15

                    I had the same disassembler issue until I noticed there was a breakpoint set for the Kate editor, for some mysterious reason. I cleared all breakpoints and returned to business as usual.

                    M 1 Reply Last reply
                    0
                    • PsnarfP Psnarf

                      I had the same disassembler issue until I noticed there was a breakpoint set for the Kate editor, for some mysterious reason. I cleared all breakpoints and returned to business as usual.

                      M Offline
                      M Offline
                      Mehdi Karimi
                      wrote on last edited by
                      #16

                      @Psnarf How did you remove all break point from Kate editor and what is kate editor or where is it? I add

                      handle SIGSTOP nopass
                      handle SIGSTOP nostop

                      options to my GDB debuger to not receive those stops. But please let me know where is the kate and how did you remove its beak points.

                      1 Reply Last reply
                      0
                      • R Offline
                        R Offline
                        Ravinie
                        wrote on last edited by
                        #17

                        Hello,

                        By removing #line directives i have fixed this issue.

                        1 Reply Last reply
                        0
                        • V VoiceShifter referenced this topic on

                        • Login

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