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. Unable to detect Windows debugging tools
Forum Update on Monday, May 27th 2025

Unable to detect Windows debugging tools

Scheduled Pinned Locked Moved Qt Creator and other tools
9 Posts 4 Posters 7.9k 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.
  • T Offline
    T Offline
    tseval
    wrote on 2 Apr 2012, 14:40 last edited by
    #1

    Hi,

    I'm trying to debug my projects with the native windows debugging tools. I have Qt Creator 2.4.1, VS2010 and the new Windows 8 SDK preview debugging tools (the only debugging tools available atm?).

    When trying to debug the program, I just get a message about not being able to detect the preferred debugger engine for debugging binaries of type x86-windows-msvc2010-pe-32bit.

    Any ideas?

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobias.hunger
      wrote on 3 Apr 2012, 08:33 last edited by
      #2

      Windows 8 SDK moved things around once again. Please try the upcoming 2.5 version of Qt Creator (I think support is there, it definitely is in master;-), that will pick up the debugger.

      1 Reply Last reply
      0
      • T Offline
        T Offline
        tseval
        wrote on 3 Apr 2012, 21:55 last edited by
        #3

        Ok, so there is no way to set up the paths manually?

        Is there a pre-built version of QtCreator 2.5 somewhere?

        Will 2.5 require Qt 5.0 btw?

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tobias.hunger
          wrote on 4 Apr 2012, 09:17 last edited by
          #4

          You can try to install the microsoft debugger tools separately. Those should get picked up just fine.

          1 Reply Last reply
          0
          • T Offline
            T Offline
            tseval
            wrote on 4 Apr 2012, 09:52 last edited by
            #5

            As far as I could see there is no standalone package for the debugger tools anymore. It's only the Win8 SDK:

            http://msdn.microsoft.com/en-us/windows/hardware/gg463009

            There is an option for installing only the debugging tools, which is what I did, but it is basically just to install the WinSDK package and uncheck all the other componets, as explained on the above webpage:

            "If you do not want an entire kit (WDK or SDK), you can install the Debugging Tools as a standalone component from the Windows SDK. In the installation wizard, select Debugging Tools, and clear other components that you don’t want."

            But are these paths really hardcoded into QtCreator? Shouldn't there be a configuration path to set these paths?

            1 Reply Last reply
            0
            • T Offline
              T Offline
              tobias.hunger
              wrote on 4 Apr 2012, 12:56 last edited by
              #6

              So far the path to the debugging tools was stable (we do look in a couple of places), so there was no need to have it configurable. Let's hope that they will stick with the current location for a while... then we do not need it configurable now either.

              Yes, I see that this is annoying for you, but we can not support 3rd party applications that were not even around at the time when we released Creator.

              1 Reply Last reply
              0
              • T Offline
                T Offline
                tseval
                wrote on 4 Apr 2012, 14:02 last edited by
                #7

                Oh, I'm not that annoyed :-) i'm just a bit surprised that it isn't configurable, at least through a config file. It wouldn't even have to be exposed in the GUI. I suppose it would have spared you for these kinds of problems when MS decides they want to move things about.

                Anyway, I'm really looking forward to2.5, especially the new refactoring stuff. Is there a planned release date yet?

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  M.Hamilton
                  wrote on 11 Apr 2012, 02:23 last edited by
                  #8

                  I had the same problem ... and I simply created a link:

                  Open a command prompt with admin rights

                  cd "\Program Files"

                  mklink /D "Debugging Tools for Windows (x86)" "C:\Program Files\WinDDK\7.1\Debuggers"

                  Did this on a Vista x86 system and everything works like a charm. Of couse you need to adapt your paths and the link name depending on your installation and system. If you're running ol' XP, get the "junction" utility from "Windows Sysinternals":http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx

                  Happy debugging!

                  Markus.

                  1 Reply Last reply
                  0
                  • R Offline
                    R Offline
                    Rochus
                    wrote on 5 Apr 2014, 09:24 last edited by
                    #9

                    Thanks Markus. That worked and solved the issue. Great.
                    I'm working with Qt 4.8 and Creator 2.4.1 on a Packard Bell Easynote 10.1 with Windows 8 and MSVC 2010 Express. I installed the 8.1 SDK and therefore had to link to "c:\Program Files\Windows Kits\8.1\Debuggers\x86".
                    Cheers
                    R.K.

                    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