RTEMS | rtems: Print thread names in the period report (!1553)

Yadi choudhary (@yadi) gitlab at rtems.org
Thu Nov 5 14:02:22 UTC 2026




Yadi choudhary commented on a discussion on cpukit/rtems/src/ratemonreportstatistics.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1553#note_161948

 >  #define PERCENT_FMT         "%04" PRId32
 >  #define NANOSECONDS_FMT     "%06ld"
 >  
 > +/* Width of the OWNER column, longer thread names are truncated */
 > +#define OWNER_NAME_WIDTH ( THREAD_DEFAULT_MAXIMUM_NAME_SIZE - 1 )

Good point, thanks. I changed it to `2 * THREAD_DEFAULT_MAXIMUM_NAME_SIZE - 1`, so the column fits the same 32-byte name buffer that the stack checker and the record code use. Longer names are still truncated to 31 characters.

Tested again on `riscv/rv64imafdc` (QEMU virt), now with a third POSIX thread that has a 40-character name:

```
    ID     OWNER                           COUNT MISSED          CPU TIME                  WALL TIME
                                                               MIN/MAX/AVG                MIN/MAX/AVG
0x42010001 imu_reader                          3      0 0.000015/0.000130/0.000066 0.000039/0.000146/0.000092
0x42010002 sensor_fusion_thread                3      0 0.000003/0.000050/0.000018 0.000018/0.000050/0.000037
0x42010003 a_very_long_thread_name_with_40     3      0 0.000002/0.000017/0.000007 0.000017/0.000045/0.000035
0x42010004 TA1                                 3      0 0.000002/0.000010/0.000005 0.000010/0.000050/0.000035
```

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1553#note_161948
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-7et4altpqn4umnuf1o1xkn58q-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/20261105/588d2d29/attachment-0001.htm>


More information about the bugs mailing list