RTEMS | bsps/mips: The exception frames and the exception report (#5691)

[Sebastian Huber (@sebhub)]

Issue created by Sebastian Huber: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5691



The link scripts of the MIPS BSPs collect the exception frames without `KEEP()`,
so `--gc-sections` removes the terminating zero word which `crtend.o`
contributes. The unwinder then walks past the end of the table and every throw
ends in a fatal exception.

An exception is reported as an interrupt rather than as an exception, so a fatal
handler receives no exception frame. `_CPU_Context_validate()` and
`_CPU_Context_volatile_clobber()` are stubs, so `spcontext01` cannot detect a
defect in the context switch.

Found while running the full test suite on the GDB simulator. This description
was created with Claude Code assistance.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5691
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-50wmha5n3440w7qyo3dq4rppb-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260817/71a5e738/attachment.htm>