RTEMS | rtems_interrupt_handler_iterate pulls in irq-record.o, replacing bsp_interrupt_get_dispatch_table_slot without CONFIGURE_RECORD_INTERRUPTS_ENABLED (#5244)

[Lucian Silistru (@lsilistr)]

Lucian Silistru created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5244



## Summary
[ticker_fail.log](/uploads/f13671152c503483e43a2812601e89d9/ticker_fail.log)

When calling rtems_interrupt_handler_iterate in code, without having CONFIGURE_RECORD_INTERRUPTS_ENABLED defined, the irq-record.o object symbols get pulled in at link time and https://gitlab.rtems.org/rtems/rtos/rtems/-/blob/main/bsps/shared/irq/irq-generic.c?ref_type=heads#L49 gets replaced by https://gitlab.rtems.org/rtems/rtos/rtems/-/blob/main/bsps/shared/irq/irq-record.c?ref_type=heads#L52

This causes handlers to be misdirected and even the first timer interrupt causes a spurious crash.

## Steps to reproduce
Apply following patch to ticker test
[ticker_iterate_record.patch](/uploads/ab614a00907a8df9d0fe960e08493b92/ticker_iterate_record.patch)

Test will fail as in [ticker_fail.log]

## Expected behaviour
Test finishes successfully

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5244
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250428/5d600fd1/attachment.htm>