Qt Forum

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

    Update: Forum Guidelines & Code of Conduct

    Unsolved the inferior stopped because it received a signal from the Operating System. Signal name : SIGSTOP Signal meaning : Stopped (signal)

    General and Desktop
    5
    8
    4346
    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.
    • L
      Lineaxe last edited by

      Does stop mean Stop? In this case Yes. I am trying to run a simple console application through debug and I get the error every time.
      the inferior stopped because it received a signal from the Operating System. Signal name : SIGSTOP Signal meaning : Stopped (signal)

      I am superior to the inferior, surely I can sort this bug out one day ?

      1 Reply Last reply Reply Quote 0
      • jsulm
        jsulm Lifetime Qt Champion last edited by

        Does your application work if you don't debug it?

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply Reply Quote 0
        • L
          Lineaxe last edited by Lineaxe

          Heh, yup it works perfectly. It is designed to be a console module that I can use as a patch that I can update when needed by the main program. It works with the program, I just run into problems when I go to using debug.
          One day I would like to find a bug with a nice easy name to digest....

          H 1 Reply Last reply Reply Quote 0
          • H
            Harkin @Lineaxe last edited by

            @Lineaxe Hi, have you fixed this issue, I got the same one, my code only "cout<<"hello world!"; it can be run, but once I'm in debug mode, the issue is happen.

            jsulm 1 Reply Last reply Reply Quote 0
            • jsulm
              jsulm Lifetime Qt Champion @Harkin last edited by

              @Harkin Can you show your code?
              Your app is working in release mode but not in debug?
              Do you have stack trace after crash?

              https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply Reply Quote 0
              • JonB
                JonB last edited by JonB

                @Harkin , @jsulm
                I don't think there is going to be a "crash" here :) It would be great if the OP/questioner stated which OS he is under when reporting this (I would if I were posting), but there you are....

                Assuming this is Linux, SIGSTOP is generated by pressing Ctrl+S at the keyboard. It pauses the program from any further attempt to output anything to the terminal. It is waiting for you to press Ctrl+Q, SIGCONT, at which point output will continue. It's for old-fashioned flow control (don't I remember this in the old terminal days!). I'm a bit hazy about this, but it may also be produced if you output to the console a binary file/something which happens to contain a 0x13 byte.

                So, I don't know how this relates to debug mode --- except, probably, if you press Ctrl+S while in the debugger it might report it this way. What debugger do you use? gdb has, IIRC, ignore ... to ignore signals....

                1 Reply Last reply Reply Quote 1
                • Aleksey_K
                  Aleksey_K last edited by

                  Solved like mentioned here:
                  https://forum.qt.io/topic/100958/catching-unix-interrupt-signal-on-console-application-when-debugging-with-qtcreator

                  JonB 1 Reply Last reply Reply Quote 0
                  • JonB
                    JonB @Aleksey_K last edited by

                    @Aleksey_K
                    ...which is indeed where I suggested telling the debugger to ignore certain signals...

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