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. Debugging in Qt creator gives SIGABRT
Forum Updated to NodeBB v4.3 + New Features

Debugging in Qt creator gives SIGABRT

Scheduled Pinned Locked Moved Unsolved General and Desktop
5 Posts 4 Posters 1.1k 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.
  • C Offline
    C Offline
    C-Cubed
    wrote on 14 Feb 2021, 15:58 last edited by
    #1

    I'm sure I'm not the first one to report this, but I haven't found any related posts.
    I am developing a simple multi-threaded application in Qt Creator (two threads).
    My second thread, worker thread, has multiple references to Qt Vectors.
    When triggering breakpoints in that thread. Qt frequently displays a message box
    saying SIGABRT. Usually at this point the Qt debugger hangs. If it doesn't I can see
    the SIGABRT is triggered by an "index out of range" error in a Qt Vector. However, the error is not in my code. I suspect the error is in Qt debugger itself and that the error is triggered while trying to evaluate a symbol or expression for display. Its very frustrating. It makes it impossible to debug using QT debugger. I'm forced to use printf's or the equivalent.
    Is there a way to suppress the assert in the Qt Vector. Is there a way to prevent the debugger from hanging?
    If I'm posting in the wrong place, please point me to the proper location.
    Thanks in advance.

    J J 2 Replies Last reply 15 Feb 2021, 06:34
    0
    • C C-Cubed
      14 Feb 2021, 15:58

      I'm sure I'm not the first one to report this, but I haven't found any related posts.
      I am developing a simple multi-threaded application in Qt Creator (two threads).
      My second thread, worker thread, has multiple references to Qt Vectors.
      When triggering breakpoints in that thread. Qt frequently displays a message box
      saying SIGABRT. Usually at this point the Qt debugger hangs. If it doesn't I can see
      the SIGABRT is triggered by an "index out of range" error in a Qt Vector. However, the error is not in my code. I suspect the error is in Qt debugger itself and that the error is triggered while trying to evaluate a symbol or expression for display. Its very frustrating. It makes it impossible to debug using QT debugger. I'm forced to use printf's or the equivalent.
      Is there a way to suppress the assert in the Qt Vector. Is there a way to prevent the debugger from hanging?
      If I'm posting in the wrong place, please point me to the proper location.
      Thanks in advance.

      J Offline
      J Offline
      jsulm
      Lifetime Qt Champion
      wrote on 15 Feb 2021, 06:34 last edited by
      #2

      @C-Cubed said in Debugging in Qt creator gives SIGABRT:

      However, the error is not in my code

      Even if it breaks inside Qt the source of the issue still can be in your code.
      Please post a stack trace after the crash.
      Also: does a debug build run without debugging without crashes?

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

      1 Reply Last reply
      0
      • C C-Cubed
        14 Feb 2021, 15:58

        I'm sure I'm not the first one to report this, but I haven't found any related posts.
        I am developing a simple multi-threaded application in Qt Creator (two threads).
        My second thread, worker thread, has multiple references to Qt Vectors.
        When triggering breakpoints in that thread. Qt frequently displays a message box
        saying SIGABRT. Usually at this point the Qt debugger hangs. If it doesn't I can see
        the SIGABRT is triggered by an "index out of range" error in a Qt Vector. However, the error is not in my code. I suspect the error is in Qt debugger itself and that the error is triggered while trying to evaluate a symbol or expression for display. Its very frustrating. It makes it impossible to debug using QT debugger. I'm forced to use printf's or the equivalent.
        Is there a way to suppress the assert in the Qt Vector. Is there a way to prevent the debugger from hanging?
        If I'm posting in the wrong place, please point me to the proper location.
        Thanks in advance.

        J Offline
        J Offline
        J.Hilk
        Moderators
        wrote on 15 Feb 2021, 07:13 last edited by
        #3

        @C-Cubed What OS, what target OS and what QtCreator, what Qt version and what debugger are we talking about here ?


        Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


        Q: What's that?
        A: It's blue light.
        Q: What does it do?
        A: It turns blue.

        1 Reply Last reply
        0
        • W Offline
          W Offline
          WildWilts
          wrote on 21 Mar 2024, 17:33 last edited by
          #4

          @jsulm
          I read my posting afterwards and thought I had been overly terse
          I am running Ubuntu 23.10 with QTCreator 12.0.2 and the tool's integrale debugger (it looks and feels like gdb). I can build, run and debug my functional code but when I try to incorporate the GUI aspects of my project

          if I build from within QTCreator I get linking errors along the lines of ":-1: error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__libc_pthread_init@GLIBC_PRIVATE'"

          If I run make from the command line the product builds fine and is executable popping up the GUI. In the make output the process makes no /snap/core20/current but uses /usr/lib to get at the *.so.0 files.

          from this I conclude I am possibly referencing the wrong object files inside QtCreator, but I have not hit on the correct way to access the reference the correct files and complete the build.

          J 1 Reply Last reply 22 Mar 2024, 06:48
          0
          • W WildWilts
            21 Mar 2024, 17:33

            @jsulm
            I read my posting afterwards and thought I had been overly terse
            I am running Ubuntu 23.10 with QTCreator 12.0.2 and the tool's integrale debugger (it looks and feels like gdb). I can build, run and debug my functional code but when I try to incorporate the GUI aspects of my project

            if I build from within QTCreator I get linking errors along the lines of ":-1: error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__libc_pthread_init@GLIBC_PRIVATE'"

            If I run make from the command line the product builds fine and is executable popping up the GUI. In the make output the process makes no /snap/core20/current but uses /usr/lib to get at the *.so.0 files.

            from this I conclude I am possibly referencing the wrong object files inside QtCreator, but I have not hit on the correct way to access the reference the correct files and complete the build.

            J Offline
            J Offline
            jsulm
            Lifetime Qt Champion
            wrote on 22 Mar 2024, 06:48 last edited by
            #5

            @WildWilts Can you show your Kit and Qt configurations in QtCreator?

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

            1 Reply Last reply
            0

            • Login

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