RTEMS | Fix potential crash issue which caused by interrupt handle logic (!473)

[Joel Sherrill (@joel)]

Joel Sherrill commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/473#note_122525


@lsilistr You got it right that "CONFIGURE_RECORD_INTERRUPTS_ENABLED is a confdef" parameter (e.g. application specific confdefs.h) and not an RTEMS build configuration parameter (e.g. waf configure config.ini). 

I think the solution is to detect whether _Record_Interrupt_initialize() has run successfully and return NULL in bsp_interrupt_get_dispatch_table_slot() when the irq records have not been initialised. Do either of you see any variables that could be checked to indicate if initialization has occurred?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/473#note_122525
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/20250512/b639a96a/attachment.htm>