Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. [SOLVED] QtCreator 2.2.1 crashes when debugging
Forum Updated to NodeBB v4.3 + New Features

[SOLVED] QtCreator 2.2.1 crashes when debugging

Scheduled Pinned Locked Moved Qt Creator and other tools
12 Posts 4 Posters 10.4k 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.
  • S Offline
    S Offline
    srikanth_trulyit
    wrote on last edited by
    #1

    Hi all,

    I am having a problem with Qt Creator 2.2.1 crashing when debugging my application.
    I am using Qt SDK 1.1 with Qt Creator 2.2.1 (based on Qt 4.7.4 32 bit), From revision 74d015d2a9

    Whenever I start debugging it shows a message as "gdb-i686-pc-mingw32.exe has stopped working" and shows a message than "gdb process is crashed". Due to this Qt Creator 2.2 is completely
    unusable for debugging. It works well if I downgrade to QtCreator 2.1, which I don't want as I would like to work on the latest QtCreator. Someone can help me how to solve this issue.

    Thanks in advance,
    Srikanth

    1 Reply Last reply
    0
    • EddyE Offline
      EddyE Offline
      Eddy
      wrote on last edited by
      #2

      I would use the updater to go to the Qt SDK 1.2 . could be a version compatibility issue

      Qt Certified Specialist
      www.edalsolutions.be

      1 Reply Last reply
      0
      • T Offline
        T Offline
        tobias.hunger
        wrote on last edited by
        #3

        It is GDB that is crashing from what I understand from your description, not Qt Creator. If that is correct: Try using the GDB from the old version of Creator if that one worked.

        1 Reply Last reply
        0
        • S Offline
          S Offline
          srikanth_trulyit
          wrote on last edited by
          #4

          Yes, it is the GDB that is crashing. QtCreator is using python based debugger (from what I see from settings). I will replace QtCreator 2.1 pythongdb with QtCreator 2.2, and update the result. Feel free to push in more suggestions :)

          1 Reply Last reply
          0
          • D Offline
            D Offline
            Duck
            wrote on last edited by
            #5

            You could post the debugger logs.

            1 Reply Last reply
            0
            • T Offline
              T Offline
              tobias.hunger
              wrote on last edited by
              #6

              ... or actually "report a bug":http://bugreports.qt.nokia.com/ with the debug log attached ...

              That way the debugger people would actually see the issue.

              1 Reply Last reply
              0
              • D Offline
                D Offline
                Duck
                wrote on last edited by
                #7

                When I think about it: Are there any firewalls active on the system, or anything else that might interfere with running processes?

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  srikanth_trulyit
                  wrote on last edited by
                  #8

                  Here is the "debug log":http://pastebin.com/gbqCBXfa.
                  python is very well installed.

                  1 Reply Last reply
                  0
                  • T Offline
                    T Offline
                    tobias.hunger
                    wrote on last edited by
                    #9

                    Are you using the GDB shipped with Qt Creator? Yours is of version 6.8 which does not yet support the Python scripting. You will need to fall back to the compiled debugging helpers for that compiler.

                    PS: Please make sure to use the GDB shipped with Qt Creator: We tend to apply some patches that help a lot with what we need of the debugger.

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      srikanth_trulyit
                      wrote on last edited by
                      #10

                      I am using gdb shipped with QtCreator. The problem came after updating to 2.2, not sure about version 6.8

                      Now I downloaded qtcreator-gdb-7.2-mingw-x86.zip from ftp://ftp.qt.nokia.com/misc/gdb/7.2/
                      Now the app is launched under debug, but breakpoints not hitting :(

                      Would like to know is it the correct gdb to use.

                      1 Reply Last reply
                      0
                      • D Offline
                        D Offline
                        Duck
                        wrote on last edited by
                        #11

                        If gdb doesn't hit a breakpoint set by file name and line number the reason is in most cases that you try to debug a binary that was not compiled with the -g option (i.e. "is not a 'Debug' build). Make sure this option appears on the g++ command line in the "Application output" pane when (re-)building the project, or pastebin the contents of this pane.

                        In any case, please also pastebin a new debugger log containing only one attempt to debug something. [The log at http://pastebin.com/gbqCBXfa contains a mix of a gdb 6.8 session, and some locally built gdb 7.2 that seems to have problems to find it's own pretty printers. Neither of these two versions of gdb have been shipped with Qt Creator, nor downloaded from ftp.qt.nokia.com.]

                        1 Reply Last reply
                        0
                        • S Offline
                          S Offline
                          srikanth_trulyit
                          wrote on last edited by
                          #12

                          Removing all assert statements in the code solved the problem, sorry for the very long delay in updating the thread.

                          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