Debugging in Qt Creator 5.15.0 doesn't work :
-
@jsulm
Thanks for the reply,
I uninstalled "Debugging Tools for Windows" and try again with same result.
Regarding the path, it's OK. I have not the same as you write because i installed Qt in an another path than "C:\Qt".
But my path is OK. The file "gdb.exe" exist in my path. I tried to uninstall all Qt and install by default in "C:\Qt" and try again with same result.
Here are some print screen :
@dahu74fr Strange.
I can't reproduce this issue on my machine.
Does this GDB work (I mean does it start in a terminal?)? -
@dahu74fr Strange.
I can't reproduce this issue on my machine.
Does this GDB work (I mean does it start in a terminal?)? -
@dahu74fr I mean open a terminal and start GDB there to see whether it works.
-
@jsulm
I started a terminal window in administrator and launch gdb.exe.
I have nothing that appear in the screen.
@dahu74fr Looks like either gdb.exe is corrupted or your anti-virus application is blocking it.
-
@dahu74fr Looks like either gdb.exe is corrupted or your anti-virus application is blocking it.
-
@jsulm
The Antivirus is the installed by Windows 10 64 bits version. Not an installed Antivirus.@dahu74fr You could try to remove MinGW and then install it again.
-
wrote on 20 Jun 2020, 10:27 last edited by dahu74fr
@jsulm
I tried to remove MinGW and install it.
Same result.
I uninstalled Qt and installed an offline later version (5.12.9).
Same result.
I don't what to do !
Perhaps a config that is not set ?
For information, i work on Windows 10 64 bits and installed Qt with "qt-unified-windows-x86-3.2.3-online.exe".
-
wrote on 13 Aug 2020, 13:47 last edited by
Did you get this going?
I wonder if you have selected the 32bit compiler rather than 64 bit?
Phil
-
wrote on 2 Oct 2020, 13:36 last edited by
I had a similar issue here with Qt installed in a non-standard location on a system with various Python's. The solution that seems to have worked is to clear the path before starting Creator. For example, by using a batch file:
set path="" python --version C:\Qt\Tools\QtCreator\bin\qtcreator.exeof course the python command fails, but it removes the red exclamation mark and "could not determine debugger type" error from the Creator dbg interface discussed above.
-
I had a similar issue here with Qt installed in a non-standard location on a system with various Python's. The solution that seems to have worked is to clear the path before starting Creator. For example, by using a batch file:
set path="" python --version C:\Qt\Tools\QtCreator\bin\qtcreator.exeof course the python command fails, but it removes the red exclamation mark and "could not determine debugger type" error from the Creator dbg interface discussed above.
