QT 5.15.0 install :

[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 :-)

[dahu74fr]

@hskoglund OK. We will look that tomorrow.
I am looking actually at the registry and there is many entries with Python.

[dahu74fr]

@hskoglund Sorry,
I couldn't try anything these 3 days. Now, it's OK.
I cleaned every entry of Python in the registry and it's the same thing.
I tried to use gdb.exe located in Qt with CodeBlocks and it works.
It's only with Qt which it doesn't works, i think.
Perhaps a Qt path ou configuration that is not good.

[hskoglund]

Hi, also the reason why Qt's gdb.exe does not work might not be Python-related at all, it could be the problem is that CodeBlock and Qt are on the same PC...
Anyways, if gdb.exe in CodeBlocks works for you, then you're ok :-)

[dahu74fr]

@hskoglund Yes Python, Qt and CodeBlocks are on the same PC.
I can uninstall Python and CodeBlocks if necessary to try if it change something.
What do you think ?

[dahu74fr]

@hskoglund Sorry,
I think that gdb in codeblocks is not working. When i launch debug in codeblocks, i have no errors. But if i want to debug step by step, i have not the options. So i think it doesn't work.

[hskoglund]

Hi, don't know so much about CodeBlocks, but their debug gdb,exe I think is Cygwin-based. Anyways, if CodeBlocks debug is broken, you could ask in their forum.

[dahu74fr]

@hskoglund I tried to launch gdb.exe whickh is in codeblocks in command line to see if it works. Inoted also that gdb.exe in codeblocks is exactly the same as in Qt. To test gdb, i used a small program prog.c:

#include <stdio.h>
#include <stdlib.h>

int main()
{
printf("Hello world!\n");
return 0;
}

The i compiled it with :

gcc -Wall -g prog.c -o prog

and after i launched :

gdb prog.exe

And the result is that i have nothing.
I made the same thing with gdb in Qt, and same result.