Panic and uncaught exception handling #60
pca006132
commented 2020-07-16 16:32:02 +08:00
- Added core ID in panic message.
- Prevented nested panic, which might happen when the kernel buffer is corrupted and the panic handler tries to obtain a backtrace through the corrupted buffer. (and libunwind would call abort which is just an alias for panic in our implementation...)
- Added error message when the kernel throws an uncaught exception to notify the user, as core1 would not be restarted currently and uncaught exception is not recoverable now.
* Added core ID in panic message.
* Prevented nested panic, which might happen when the kernel buffer is corrupted and the panic handler tries to obtain a backtrace through the corrupted buffer. (and libunwind would call abort which is just an alias for panic in our implementation...)
* Added error message when the kernel throws an uncaught exception to notify the user, as core1 would not be restarted currently and uncaught exception is not recoverable now.
sb10q
closed this pull request 2020-07-16 17:11:36 +08:00
No reviewers
Labels
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/artiq-zynq#60
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "pca006132/artiq-zynq:exception"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?