Issue created by Sebastian Huber: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5692
The BSP installs the interrupt prologue of the interrupt manager on all vectors, so a processor exception is dispatched as an interrupt with no handler and ends as a spurious interrupt. A divide by zero terminates the run and `spfatal26` takes no exception at all. The prologue is also wrong for the ten vectors on which the processor pushes an error code, because the frame it assumes has none. `_CPU_Instruction_illegal()` emits a `.word 0`, which is a valid add instruction on x86, so nothing is raised. The vector operations of the interrupt manager are stubs, the BSP has no way to raise an interrupt in software and no `tm27` support, the vector count is wrong, and the acknowledge happens in the wrong place for a nested interrupt. `_CPU_Context_validate()` is a stub as well. Found while running the full test suite on Qemu. This description was created with Claude Code assistance. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5692 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-9jm6zalj1p2t6o7zt38l9nck6-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
