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. Segmentation fault, SIGSEGV
Qt 6.11 is out! See what's new in the release blog

Segmentation fault, SIGSEGV

Scheduled Pinned Locked Moved General and Desktop
6 Posts 3 Posters 5.0k 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.
  • Z Offline
    Z Offline
    zakirenish
    wrote on last edited by
    #1

    m

    1 Reply Last reply
    0
    • Z Offline
      Z Offline
      zakirenish
      wrote on last edited by
      #2

      h

      1 Reply Last reply
      0
      • G Offline
        G Offline
        goetz
        wrote on last edited by
        #3

        Where does the segfault happen? Best would be to run your program in debug mode. You usually should be shown the line where the crash happens.

        PS: please wrap your code in @-tags, not in [ code ].

        http://www.catb.org/~esr/faqs/smart-questions.html

        1 Reply Last reply
        0
        • Z Offline
          Z Offline
          zakirenish
          wrote on last edited by
          #4

          well thats the problem i dont see the line in my code where it gives the problem. I run in debugger mode.
          shows error in some Qt header file: qscopedpointer.h

          piece of code:

          @
          inline T *data() const
          {
          return d; <<<<<< points to here
          }

          inline bool isNull() const
          {
              return !d;
          }
          

          @

          Thanks

          1 Reply Last reply
          0
          • L Offline
            L Offline
            loladiro
            wrote on last edited by
            #5

            Two things you can try:

            Analyze the backtrace to see where the SIGSEGV happens.

            Use reverse debugging

            1 Reply Last reply
            0
            • G Offline
              G Offline
              goetz
              wrote on last edited by
              #6

              Somehwere further down, the backtrace of the segfault should show you the line in your code that triggered the error.

              http://www.catb.org/~esr/faqs/smart-questions.html

              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