After a long work on debugging GDB crashed with segmentation fault

[Ian Ilyasov]

I've been debugging PostgreSQL REL_14_STABLE branch authentication code starting the postgres postmaster, running psql and then connecting to a new process using `sudo gdb -p <pid>`. After a long day of it, I met this segmentation fault. This message says, that it is definitely a bug and I should report it, but GDB site says, that probably I should firstly message it to the distributor, which for my laptop(x86_64) OS Ubuntu 22.04 is Ubuntu.

```
Fatal signal: Segmentation fault
----- Backtrace -----
0x5555556f0077 ???
0x5555557f2859 ???
0x5555557f2a22 ???
0x7ffff6c4251f ???
    ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x7ffff6db1ebc ???
    ../sysdeps/x86_64/multiarch/strlen-evex.S:77
0x5555559b1671 ???
0x5555559b1ba4 ???
0x5555559b208f ???
0x5555559b2b89 ???
0x5555559c1381 ???
0x5555559c14be ???
0x55555585b7f6 ???
0x555555a387a8 ???
0x55555585ea1e ???
0x55555584e171 ???
0x555555851308 ???
0x555555845b64 ???
0x55555586b9d4 ???
0x555555ba4815 ???
0x555555ba4cf9 ???
0x555555a1aaab ???
0x5555558afa00 ???
0x5555558b1a16 ???
0x5555558b204e ???
0x55555564815f ???
0x7ffff6c29d8f __libc_start_call_main
    ../sysdeps/nptl/libc_start_call_main.h:58
0x7ffff6c29e3f __libc_start_main_impl
    ../csu/libc-start.c:392
0x55555564dbf4 ???
0xffffffffffffffff ???
---------------------

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

The only way I could reproduce this bug is to reboot and do debug using gdb all day like I described in the begging of the message.

Sorry, if I provided little info.