QT 5.15.0 install :

[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.

[hskoglund]

When you typegdb prog.exe and then type start inside gdb it should say something like:
...
Temporary breakpoint 1 at 0x40.... .... prog.c line 6.
Starting program...
...

But your gdb.exe is just silent, same as before?

[dahu74fr]

@hskoglund Yes it is silent when i type gdb prog.exe ,
But between the command gdb prog.exe and when it returns : "C:\Programmation\Qt\Tools\mingw810_64\bin>" the computer works about 5 seconds.

[hskoglund]

Yeah, it's trying to start Python I think.

One idea you haven't tried (I think): go to Settings and create a new user, logout and login as the new user. Then try gdb.exe when logged in as that new user.

[dahu74fr]

@hskoglund OK. I try.

[dahu74fr]

@hskoglund I tried with a new account and i have the same thing.

[hskoglund]

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...

[dahu74fr]

@hskoglund Yes it seams to work :

and :

[hskoglund]

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.exe

Now 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

[dahu74fr]

@hskoglund
I think you have 2315 entries when you look at the bottom of the window. For me i have 362 entries only.

I tried an other time and now 356 entries.

[hskoglund]

Ok, could you scroll down in the ProcMon window, so the last lines (before it stops) of the output is shown?

[dahu74fr]

@hskoglund Here are the latest lines :

And with scroll on the right :

[hskoglund]

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).