QT 5.15.0 install :
-
Yeah, sorry I meant C:\Programmation\Qt\Tools\mingw810_64\bin.
Also, try this in the same CMD window as above:
gdborig
-
@hskoglund I tried in my previous post. Here was the result :
-
You mean typing
gdborig
also returns nothing? -
@hskoglund Yes i have an error message :
-
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
-
@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 :
-
Hmm, tricky :-) one more, in the same CMD try:
C:\Programmation\Qt\Tools\mingw810_64\opt\bin\gdbmtool.exe
-
@hskoglund
I have also Python installed on my computer. The V3.8.3.
Result :
-
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
-
@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
-
-
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
-
@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. -
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
-
@hskoglund said in QT 5.15.0 install ::
set PYTHONHOME=C:\Programmation\Qt\Tools\mingw810_64\opt
There is now no error with dbgorig.
-
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 siteIf it does not, could you type:
set
-
-
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) -
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. -
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#StartupSo 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 :-)
41/77