Enable GDB for binutils 2.40 and fix native AmigaOS debugging - #46
Enable GDB for binutils 2.40 and fix native AmigaOS debugging#46derfsss wants to merge 1 commit into
Conversation
Binutils build changes: - Enable GDB in both cross and native 2.40 builds (remove --disable-gdb) - Add --with-python=no to native build configuration GDB native debugging fixes (patch 0002): - Fix register fetch/store: correct GPR/FPR indexing, implement WriteTaskContext for store_registers, gate AltiVec on ECF_VECTOR - Fix trap numbers: use SDK TRAPNUM_* values from exec/interrupts.h instead of raw PPC vector offsets - Implement attach() for connecting to running processes - Fix kill() to use Signal+RestartTask instead of DeleteTask - Add message pool safety with Forbid/Permit and NULL checks - Fix BFD file cache: skip realpath on AmigaOS to prevent path mangling (assigns like T: resolve to "RAM Disk:T/" which fails) - Fix charset: force UTF-8 host charset on AmigaOS (clib4 iconv) Test infrastructure: - Add GDB test targets to tests/makefile (test-gdb-all, test-gdb-smoke, test-gdb-load, test-gdb-disasm, test-gdb-remote) - Add docs/ to .gitignore Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Sadly does not compile for me because of some GCLIBC includes hack: binutils-native-build-2.40/gnulib/import/wchar.h That might be caused by a difference in the CLIB4 headers between the cross-compiler and clib4 repo. The |
|
But building a cross compiler with adtools fails because of this: |
|
I was able to build adtools with gcc 13 and binutils 2.40 but without gdb. |
|
I was able to build adtools with gcc 13 and binutils 2.40 but without gdb.
No, the issue is that we need to set the But then the compilation fails with: |
Binutils build changes:
GDB native debugging fixes (patch 0002):
Test infrastructure: