QT 5.15.0 install :
-
@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 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. -
About why python does not work good for gdb, could you check the python installation in Qt:
cd C:\Programmation\Qt\Tools\mingw810_64\opt\bin python -c "print 2+2"If the python command works and prints "4" then could you try the same with the verbose flag:
python -v -c "print 2+2"and post the output here...
-
Ok, looks good. I think to see why your gdb.exe does not run, we need to trace it using Process Monitor, download it here
Here's what you do:
start Process Monitor (procmon.exe), type ctrl+L to show the Filter dialog box, in that dialog in the top left corner, in the drop-down list, select "Process Name", then check that the next drop-down list selects "Is" then in the edit box type gdborig.exe and the click the Add button. After that it should look like this:
Click OK button to close the dialog box.Then start gdb.exe as we did before:
C:\Programmation\Qt\Tools\mingw810_64\bin\gdb.exeNow entries should be seen in ProcMon, like this:
My ProcMon shows 2315 entries for gdborig.exe but your output should be shorter (since it fails) post here say the last 50 lines before it stops.Note: you can clear the display of ProcMon using ctrl+X
-
Thanks, now I can see the gdborig.exe crash in the Procmon output (the C:\Windows\System32\WerFault.exe line)
To see the crash info, click on the Start button and type event then select Event Viewer
In the left column, select Windows Logs and then click on Application, then in the middle window, in the Source column, do you see any gdborig lines? If yes, click on them to see more info in the lower (General) window.Edit: gdborig.exe seems to crash when trying to read the C:\msys64\etc\termcap file. If you have MSYS2 installed, try removing or renaming that file.
Or you could try removing MSYS2 completely (click on Start button, type add or , select Add or Remove programs then search for MSYS2 64-bit in the list, click on it and select Uninstall).
