Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Debugger does not work on Windows 7/64 with SDK 1.2
QtWS25 Last Chance

Debugger does not work on Windows 7/64 with SDK 1.2

Scheduled Pinned Locked Moved Installation and Deployment
5 Posts 3 Posters 2.7k 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.
  • H Offline
    H Offline
    Hanno
    wrote on last edited by
    #1

    Since some time in January / February 2012, I can no longer use the debugger under Windows 7 / 64, so I do the work under MAC OS. I have now tried a clean installation of SDK 1.2 on thee different PCs (no Visual Studio, Mingw 4.4 QT 4.8.0 desktop, QT Creator 2.4.1)
    When I start debugging, I get a message saying that the gdb process has crashed.

    Before I had been happy with this type of installation. What has changed? Any ideas? What is to be done besides a clean SDK installation?
    Any help is appreciated.
    Hanno

    1 Reply Last reply
    0
    • jensen82J Offline
      jensen82J Offline
      jensen82
      wrote on last edited by
      #2

      Which GDB? Are you using the python-enabled gdb? In QtCreator go to "Options->"Build and Run"->"Toolchains" and choose yours. What's in the line "Debugger:" ?

      1 Reply Last reply
      0
      • H Offline
        H Offline
        Hanno
        wrote on last edited by
        #3

        I was using C:\QtSDK\mingw\bin\gdb.exe.

        Now I have changed to C:\QtSDK\pythongdb\python_2.7based\gdb-i686-pc-mingw32.exe
        and am happy.

        Thanks a lot!
        Hanno

        P.S.
        Why is the default setting blank and not editable?

        1 Reply Last reply
        0
        • jensen82J Offline
          jensen82J Offline
          jensen82
          wrote on last edited by
          #4

          Good work! I have no idea...i think the default-value is set by toolchain...

          1 Reply Last reply
          0
          • F Offline
            F Offline
            Fazer
            wrote on last edited by
            #5

            I had the exact same problem, thanks for solution!

            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