On Tue, Feb 4, 2025 at 5:21 PM <devel-request(a)lists.crash-utility.osci.iowrote: Revert longaarch related gdb changes As you mentioned in patch log, the above two patches are no longer needed, which are included in gdb 16.2. So I would suggest removing them from gdb-16.2.patch, revert is not very good in the gdb upgrade case. For LoongArch, also remove crash part changes(it may not work), once the gdb-16.2 upgrade is ready, the LoongArch people can follow the current changes and get a clean patch, maybe two or three hundred lines of code. Update to gdb-16.2 I tend to have a clean patch for gdb-16.2 rather than based on gdb-10.2.patch, and which is easier to maintain in the future. BTW: for several build failure patches, I would suggest handling them firstly. If we can not merge the gdb-16.2 patch in time, there may be risks. What do you think? Thanks Lianbo > Makefile | 3 + > configure.c | 21 +- > crash_target.c | 6 +- > defs.h | 8 +- > gdb-10.2.patch | 16241 ---------------------------------------------- > gdb-16.2.patch | 2258 +++++++ > gdb_interface.c | 18 +- > kernel.c | 6 +- > symbols.c | 4 +- > tools.c | 6 +- > 10 files changed, 2304 insertions(+), 16267 deletions(-) > delete mode 100644 gdb-10.2.patch > create mode 100644 gdb-16.2.patch > -- > 2.47.0