GDB segfaults when using Ctrl-C to interrupt attached process

[exposedcranium]

Description / Steps to reproduce the issue

1. Launch MSYS2 terminal.
2. Run "gdb".
3. Attach to a running process with "attach <pid>".
4. Press "c" to continue past initial breakpoint.
5. Press Ctrl-C to interrupt (break) execution.
6. Segfault

Expected behavior

Program is interrupted and return to GDB console.

Actual behavior

Segmentation fault:

Fatal signal: Segmentation fault
----- Backtrace -----
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

Segmentation fault (core dumped)

Verification

• I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

MSYS_NT-10.0-22000

Are you willing to submit a PR?

No idea how to fix.

[Biswa96]

What is the output of type gdb ?

[exposedcranium]

Ended up switching to mingw64's gdb implementation instead of MSYS' which works fine. Will try again when I get the chance. (btw, why do we need both?)