The Latest stable update Completely broke GDB, it is literally UNUSEABLE now, i don’t know how this didn’t get found in testing, but it didn’t. Every single attempt to attach to a 32bit or 64bit program fails with
LWP 50578: generic error
Example output when attaching to a 32 bit Application:
GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) attach 55917
Attaching to process 55917
[New LWP 55918]
[New LWP 55919]
[New LWP 55920]
[New LWP 55921]
[New LWP 55922]
[New LWP 55923]
[New LWP 55924]
[New LWP 55925]
[New LWP 55926]
[New LWP 55927]
[New LWP 55928]
[New LWP 55929]
[New LWP 55930]
[New LWP 55931]
[New LWP 55932]
[New LWP 55933]
[New LWP 55934]
[New LWP 55935]
[New LWP 55936]
[New LWP 55940]
[New LWP 55941]
[New LWP 55942]
[New LWP 56011]
[New LWP 56013]
[New LWP 56014]
warning: Could not load shared library symbols for bin/launcher.so.
Do you need "set solib-search-path" or "set sysroot"?
Error while reading shared library symbols for /usr/lib32/libpthread.so.0:
Cannot find user-level thread for LWP 56014: generic error
0xf7f08b59 in __kernel_vsyscall ()
(gdb) c
Continuing.
[LWP 56014 exited]
Cannot find user-level thread for LWP 56044: generic error
(gdb) q
A debugging session is active.
Inferior 1 [process 55917] will be detached.
Quit anyway? (y or n) y
Aborted
As you can see, the error pops up whenever you try to do anything, you cannot even unpause the program while gdb is attached, and any kind of actions will fail entirely.
Steps to reproduce:
sudo gdb
attach (any pid)
- It fails