RTEMS | Backport: cpukit: Raise internal error if we cannot open stdin with fileno 0 (!762)

[Jeremy Lorelli (@jjl77)]

Jeremy Lorelli created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/762

Project:Branches: jjl77/rtems:pr-6-mvme3100-fix to rtems/rtos/rtems:6
Author:   Jeremy Lorelli




## Summary

cpukit: Raise internal error if we cannot open stdin with fileno 0

If someone manages to open a file before rtems_libio_post_driver is run,
open() may allocate a file number other than 0 for stdin. This leads to
a silent failure of the logic in rtems_libio_post_driver, and confusing
behavior because your BSP behaves as if it doesn't have a console.

Instead of failing silently, raise an internal error if open() succeeds
but gives us an unexpected file number for stdin.


<!-- Default settings, if it is a dropdown it will set after submission -->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/762
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/20251003/20ad52b7/attachment.htm>