gdbserver, Failed to read memory at 0xfffffffe about openocd HOT 1 CLOSED

Hi,

I acknowledge the issue you have noticed, and confirm that we can reproduce.

We have identified that this issue is mainly caused by bad call stack management at gdb level.
Thus we reported the issue to gdb community (please refer to https://sourceware.org/bugzilla/show_bug.cgi?id=28549 )

Several tentative have been done to fix the gdb stack unwinder, but this required much effort.
Currently there is a promising patch series (at gdb mailing list https://sourceware.org/pipermail/gdb-patches/2022-January/185131.html).

I will keep you posted whenever this is merged upstream.
Once done, you will need to rebuild gdb binary ( if you are using your own toolchain ).
At STM32CubeIDE level, we will try to include the fixed ASAP.

Thank you for reporting this.
Regards,
Tarek

from openocd.