N64 ROM crashes after attaching with gdb-multiarch

[maxgerhardt]

Describe the bug
A breakage was introduced for the gdb server for Nintendo64. v139 works, starting with v140 up to the latest bleeding edge does not work. When launching Ares with the GDB server turned on (localhost:9123) and a ctest.z64 rom produced by this libdragon example, and the connecting to it with gdb-multiarch ctest.elf, setting a breakpoint at main, continuining to it, and then continuing again will make the ROM crash. This does not happen on Ares v139, where the execution continue normally. This makes debugging N64 games on the latest Ares impossible.

To Reproduce
Steps to reproduce the behavior:

1. Download and extract ctest.zip
2. Launch gdb-multiarch within the extracted directory with gdb-multiarch -ex "target extended-remote :9123" -ex "break main" -ex "continue" build/ctest.elf
3. Quickly after that, launch the latest Ares with ./ares ctest.z64
4. gdb-multiarch should now connect to Ares
5. Bleeding-Edge Ares crashes instantly, v141 & v140 will crash after a "continue", v139 will work normally

Expected behavior

After hitting the breakpoint in main() and hitting continue, the game should continue normally and not crash.

Screenshots
Ares bleeding-edge version after the "continue"

Ares v141 after the "continue"

Ares v139 after the "continue"

Additional context
Working with Ubuntu 24.10, GDB-multiarch 15.1 (sudo apt install gdb-multiarch).