Greeting!
About 4 month ago, I posted a topic about "MSYS2 Mingw32 GDB crashed just at
first breakpoint". The old topic can follow this link:
https://sourceforge.net/p/msys2/mailman/message/35673225/
Now, the problem above is sloved, and the sample program can be well debugged
at bash command line. However, In Qt -creator (both x64 and x86), there is
still a strange problem when gdb hits the first breakpoint .
This signal triggered an message box below:
Signal Recieved
"The inferior stopped because it recieved a signal from the operation system"
Signal name: ?
Signal meaning: Unknown signal
I notice that in mingw32 32-bit qtcreator, a x64 gdb is called:
dStart parameters: 'gdbtest' mode: 1
dABI: x86-windows-msys-pe-32bit
dLanguages: c++
dExecutable: C:\msys64\home\user\gdbtest\test.exe
dDirectory: C:\msys64\home\user\gdbtest
dDebugger: C:\msys64\mingw64\bin\gdb.exe
So, I grep config files and located the default profile file:
C:\msys64\mingw32\share\qtcreator\QtProject\qtcreator\profile.xml
but could not find how to change the default debugger for mingw32 qt.
Finally, I clone a config from x86, and assign GDB x86 as the debugger,
everything is OK.
This is a simple problem, I think, may be someone can next patch will fix
this.
---------------------------------
MSYS2 is an amazing project!
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Msys2-users mailing list
Msys2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/msys2-users
