QT 5.15.0 install :

[hskoglund]

Yeah, sorry I meant C:\Programmation\Qt\Tools\mingw810_64\bin.
Also, try this in the same CMD window as above:
gdborig

[dahu74fr]

@hskoglund I tried in my previous post. Here was the result :

[hskoglund]

You mean typing gdborig also returns nothing?

[dahu74fr]

@hskoglund Yes i have an error message :

[hskoglund]

The error message is correct, but could also check that MinGW's python works, try type:

C:\Programmation\Qt\Tools\mingw810_64\opt\bin\python

[dahu74fr]

@hskoglund said in QT 5.15.0 install ::

C:\Programmation\Qt\Tools\mingw810_64\opt\bin\python
I have also Python installed on my computer. The V3.8.3.
Here the result :

[hskoglund]

Hmm, tricky :-) one more, in the same CMD try:

C:\Programmation\Qt\Tools\mingw810_64\opt\bin\gdbmtool.exe

[dahu74fr]

@hskoglund
I have also Python installed on my computer. The V3.8.3.
Result :

[hskoglund]

Sure, but your V3.8.3 I think should not bother MinGW's version of python.
One more check: in that same CMD, type:

set path=C:\Programmation\Qt\Tools\mingw810_64\bin;C:\Programmation\Qt\Tools\mingw810_64\opt\bin
gdborig

[dahu74fr]

@hskoglund said in QT 5.15.0 install ::

set path=C:\Programmation\Qt\Tools\mingw810_64\bin;C:\Programmation\Qt\Tools\mingw810_64\opt\bin

[hskoglund]

Hmm, you could be right, that your installed Python V3.8.3 is bullying MinGW's python 2.7, because on my Windows 10 without any Python 3.8.3 installed, when I set the path set path=C:\Qt\Tools\mingw810_64\bin;C:\Qt\Tools\mingw810_64\opt\bin and type gdborig this shows:

[hskoglund]

Ok, to try workaround the fighting of the Pythons, in that same CMD window, type;

set PYTHONHOME=C:\Programmation\Qt\Tools\mingw810_64\opt

then try both

gdborig

and

gdb

[dahu74fr]

@hskoglund
For information, before launching what you wrote, i have uninstalled Python 3.8.3, also a Python 2.7.4 used by a software and uninstalled Qt with RevoUninstaller.
Then i rebooted and made a cleanup of the registry with CCleaner.
I reinstalled Qt, but i have the same result in Debugger in Options.
And same result with what you wrote.

The result for gdborig :

And for gdb :

[hskoglund]

Maybe some remnants of Python 3 remains, what happens if you try the same as before in that CMD window, i.e.:

set path=C:\Programmation\Qt\Tools\mingw810_64\bin;C:\Programmation\Qt\Tools\mingw810_64\opt\bin
set PYTHONHOME=C:\Programmation\Qt\Tools\mingw810_64\opt
gdborig
gdb

[dahu74fr]

@hskoglund said in QT 5.15.0 install ::

set PYTHONHOME=C:\Programmation\Qt\Tools\mingw810_64\opt

There is now no error with dbgorig.

[hskoglund]

Ok, if you set an empty PYTHONHOME:

set PYTHONHOME=

and then if you try

gdborig

again, then it should say:
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
ImportError: No module named site

If it does not, could you type:

set

[dahu74fr]

@hskoglund said in QT 5.15.0 install ::

set PYTHONHOME=

[hskoglund]

The set output looks totally legit, the only left I think (a bit of a longshot :-):
try uninstalling the Component Servicing Infrastructure (CSI) program, (perhaps that csilogfile tracing stuff messes with gdb)

[dahu74fr]

OK.
I don't know how to uninstall the Component Servicing Infrastructure (CSI) program.
Can you tell me how ?
I will try this tomorrow.
I will also look at the registry because on my computer, i have a software who check if i have the latest versions for my softwares.
And this software tells me that i have an old version of Python (V3.7.4), or i have uninstalled all versions of Python.
So i thing something is staying in the registry.
I will send my feedback when it will be done.
Best regards and thanks a lot.

[hskoglund]

Uninstall CSI program: no problem, we can try that later.
Also, I just googled for how to trace the startup of gdb
https://www.sourceware.org/gdb/onlinedocs/gdb.html#Startup

So the culprit is that gdborig does not show those error lines as I mentioned above (it just exits silently)

We can look into that tomorrow :-)