RTEMS | score: A time of day beyond the year 2400 breaks the realtime watchdogs (#5749)

Sebastian Huber (@sebhub) gitlab at rtems.org
Thu Sep 3 02:36:24 UTC 2026



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



`rtems_clock_set()` accepts every year up to `TOD_LATEST_YEAR`, which is 4095.
`_TOD_Set()` asserts that the time of day meets
`_TOD_Is_valid_new_time_of_day()`. That check stops at the year 2400, so a
debug build ends `spclock_err02` and `ts-validation-no-clock-0` with a failed
assertion.

A release build hands the tickle of the realtime watchdogs a wrapped value,
because the seconds field of the watchdog ticks holds 34 bits alone.

Found while running the test suite with `RTEMS_DEBUG`. This description was
created with Claude Code assistance.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5749
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-dm5bkxc2xuk6wrjaiz5lu5xfg-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/20260903/45bc6092/attachment-0001.htm>


More information about the bugs mailing list