RTEMS | Improve event record handling (!282)

Sebastian Huber (@sebhub) gitlab at rtems.org
Fri Nov 1 05:58:09 UTC 2024




Sebastian Huber commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/282#note_114189


It is unlikely that a user will notice the API changes. The user can configure the event recording through application configuration options (which didn't change). The user can also generate events with functions not changed by this patch set. Getting the event records to the host is done through the dump functions (which didn't change) or a TCP stream. Since the record format version changed, you need matching tools.

I am sure there are lots of ways to improve how this is organized, however, I have only a limited amount of time which I can dedicate to this work. The patch set fixes some serious reliability issues. It was on my TODO list for a long time. I prioritized the work just for the release.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/282#note_114189
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/20241101/bc070e47/attachment.htm>


More information about the bugs mailing list