Could not determine debugger type

8Observer8

I use:

Qt Creator 13.0.0
Qt 6.6.3
Windows 10

I have made a clone of the Kit with manual debugger's settings:

It works but I cannot delete the bad Kit because the "Remove" button is inactive for debugger and Kit. Can I solve it or delete? Because I don't want to see it here:

Axel Spoerl

@8Observer8

Please try two things:

call gdb.exe --version, to confirm that gdb itself isn't broken.
just because I see Python in your kits: Check the pythonpath system variable in your advanced system settings and try removing it completely. I have vague memories of a stack-overflow thread, which found out that gdb might not get found with certain paths in that variable. Just couldn't find it right now, it's been a few years.....

cristian-adam

The auto-detected debuggers are actually being set up by sdktool.

Their configuration is saved in C:\Qt\Tools\sdktool\share\qtcreator\QtProject\qtcreator\debuggers.xml. For some reason your configuration is broken.

Mine looks like this:

 <data>
  <variable>DebuggerItem.0</variable>
  <valuemap type="QVariantMap">
   <valuelist type="QVariantList" key="Abis">
    <value type="QString">x86-windows-msys-pe-64bit</value>
   </valuelist>
   <value type="bool" key="AutoDetected">true</value>
   <value type="QString" key="Binary">C:/Qt/Tools/mingw1120_64/bin/gdb.exe</value>
   <value type="QString" key="DisplayName">GNU gdb 11.2.0 for MinGW 11.2.0 64-bit</value>
   <value type="int" key="EngineType">1</value>
   <value type="QString" key="Id">Debugger.qt.tools.win64_mingw900</value>
  </valuemap>
 </data>

8Observer8

Mine is the same. I even tried to compare yours file with mine using https://text-compare.com/ I mean from <data> to </data>

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE QtCreatorDebuggers>
<!-- Written by sdktool , 2024-04-16T17:42:52. -->
<qtcreator>
 <data>
  <variable>DebuggerItem.0</variable>
  <valuemap type="QVariantMap">
   <valuelist type="QVariantList" key="Abis">
    <value type="QString">x86-windows-msys-pe-64bit</value>
   </valuelist>
   <value type="bool" key="AutoDetected">true</value>
   <value type="QString" key="Binary">C:/Qt/Tools/mingw1120_64/bin/gdb.exe</value>
   <value type="QString" key="DisplayName">GNU gdb 11.2.0 for MinGW 11.2.0 64-bit</value>
   <value type="int" key="EngineType">1</value>
   <value type="QString" key="Id">Debugger.qt.tools.win64_mingw900</value>
  </valuemap>
 </data>
 <data>
  <variable>DebuggerItem.Count</variable>
  <value type="int">1</value>
 </data>
 <data>
  <variable>Version</variable>
  <value type="int">1</value>
 </data>
</qtcreator>

@Axel-Spoerl said in Could not determine debugger type:

call gdb.exe --version, to confirm that gdb itself isn't broken

>gdb.exe --version
GNU gdb (GDB) 11.2

@Axel-Spoerl said in Could not determine debugger type:

just because I see Python in your kits: Check the pythonpath system variable in your advanced system settings and try removing it completely. I have vague memories of a stack-overflow thread, which found out that gdb might not get found with certain paths in that variable. Just couldn't find it right now, it's been a few years.....

I didn't find pythonpath. What is advanced system settings?

Axel Spoerl

I didn't find pythonpath. What is advanced system settings?

I am not a Windows specialist, but you can check here.

8Observer8

When I installed Python I set "Add Python 3.8 to path":

The path was added to the user Path variable or I added the path manually. I don't remember:

I cannot see the system Path variable because the Edit button is inactive:

I tried temporary to remove the E:\ProgramFiles\Python\Python38\ path from the user Path and I don't have any warnings:

And Python works too in the CMD. I think I don't need to add Python to the user Path variable manually. I didn't think Python could affect GDB. Without you, I would not have solved this problem. Thank you very much!