Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Update: Forum Guidelines & Code of Conduct


    Qt World Summit: Early-Bird Tickets

    Unsolved Qt Creator unable to start debugger

    Tools
    3
    4
    273
    Loading More Posts
    • 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.
    • M
      mjohn last edited by

      When I click 'Start Debugging' (F5) I immediately get an error dialog saying:
      "The inferior stopped because it received a signal from the operating system."
      Signal name: SIGSEGV

      So something got a segmentation fault but I'm not able to determine what that is. From the 'Application Output' window it only prints out 'Debugging starts'. The application runs normally outside of the debugger (Ctrl+R).
      This is on Linux Mint (Debian 9 base) with Qt Creator 4.5.1.

      aha_1980 1 Reply Last reply Reply Quote 1
      • mrjj
        mrjj Lifetime Qt Champion last edited by

        Hi
        Sorry for the wait. you post must have gone under the radar.

        Did you check what GDB you have installed?

        https://doc.qt.io/qtcreator/creator-debugger-engines.html
        " The minimum supported version is GDB 7.5 using Python version 2.7, or 3.3, or newer."

        1 Reply Last reply Reply Quote 3
        • aha_1980
          aha_1980 Lifetime Qt Champion @mjohn last edited by

          Hi @mjohn,

          just to add to @mrjj, the Debugger Log under Windows > Views might give some more insight what's going on.

          Regards

          Qt has to stay free or it will die.

          M 1 Reply Last reply Reply Quote 3
          • M
            mjohn @aha_1980 last edited by

            Hi @aha_1980,
            This provided some useful additional info, which I've attached below.

            >408^running
            dNOTE: ENGINE RUN AND INFERIOR RUN OK
            sRunning.
            dState changed from EngineRunRequested(7) to InferiorRunOk(11)
            dNOTE: ENGINE RUN AND INFERIOR RUN OK
            sRunning.
            dState changed from EngineRunRequested(7) to InferiorRunOk(11) [master]
            dINFERIOR STARTED
            sApplication started.
            >*running,thread-id="all"
            dNOTE: INFERIOR STILL RUNNING IN STATE InferiorRunOk.
            
            >~"\nProgram"
            >~" received signal SIGSEGV, Segmentation fault.\n"
            >~"0x0000000000000000 in ?? ()\n"
            >*stopped,reason="signal-received",signal-name="SIGSEGV",signal-meaning="Segmentation fault",frame={addr="0x0000000000000000",func="??",args=[]},thread-id="1",stopped-threads="all",core="1"
            dNOTE: INFERIOR SPONTANEOUS STOP
            sStopped.
            dState changed from InferiorRunOk(11) to InferiorStopOk(14)
            dNOTE: INFERIOR SPONTANEOUS STOP
            sStopped.
            dState changed from InferiorRunOk(11) to InferiorStopOk(14) [master]
            <409importPlainDumpers off
            dHANDLING SIGNAL SIGSEGV
            sStopped: Segmentation fault (Signal SIGSEGV).
            

            The GDB version that it found is version 7.12.0.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post