os: Include errno and TCB pterrno in assert logs #7093
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add current errno and task-specific pterrno to the assertion detail logs. [Global IRQ errno] ``` =========================================================== Assertion details =========================================================== Assertion failed CPU0 at file: chip/amebasmart_timerisr.c line 70 irq: 27 print_assert_detail: Assert location (PC) : 0x0e028459 check_assert_location: Code asserted in IRQ state! check_assert_location: IRQ num: 27 check_assert_location: IRQ handler: 0e0283f5 check_assert_location: IRQ errno: 0 =========================================================== ``` [TCB errno] ``` =========================================================== Asserted task's TCB info =========================================================== task_show_tcbinfo: State : 4 task_show_tcbinfo: Flags : 6 task_show_tcbinfo: Errno : 0 task_show_tcbinfo: Lock count : 0 task_show_tcbinfo: Timeslice : 0 task_show_tcbinfo: Waitdog : 0 task_show_tcbinfo: WaitSem : 0 task_show_tcbinfo: MsgwaitQ : 0 task_show_tcbinfo: Sigdeliver : 0 task_show_tcbinfo: Nsyscalls : 0 =========================================================== ``` Signed-off-by: seokhun-eom <[email protected]>
8adfc08 to
3ff3ecb
Compare
ewoodev
reviewed
Dec 22, 2025
Contributor
ewoodev
left a comment
There was a problem hiding this comment.
Could you please explain more why we need errno in assertion log?
Contributor
Author
This change was inspired by the following code snippet. In code like the above, when an assertion occurs, it is difficult to determine the exact errno value that was set at the time of the failure. |
- Update TCB and IRQ information parsing to display errno - Implement init_errno_info() to map errno values to description [Trap tool example] ``` 5. Assertion Data during interrupt mode: - Interrupt handler at addr Symbol_name 0xe0283b5 bsp_pm_domain_control - Interrupt number : 27 - Interrupt errno : 9 - EBADF(Bad file number) t. Asserted TCB info: State : Inactive Flags : 6 - Kernel Thread - Non-cancellable Pthread Errno : 22 - EINVAL(Invalid argument) Lock count : 0 Timeslice : 0 Waitdog : 0 WaitSem : 0 MsgwaitQ : 0 Sigdeliver : 0 Nsyscalls : 0 ``` Signed-off-by: seokhun-eom <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add current errno and task-specific pterrno to the assertion detail logs.
[Global IRQ errno]
[TCB errno]
tools/trap: Add errno mapping and display for assert logs
[Trap tool example]