-
-
Notifications
You must be signed in to change notification settings - Fork 17.5k
Why does teeos panic during exit? #162847
Copy link
Copy link
Open
Labels
C-bugCategory: This is a bug.Category: This is a bug.O-teeosTarget: Arm's secure enclave that code isn't supposed to be able to jailbreakTarget: Arm's secure enclave that code isn't supposed to be able to jailbreakT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Description
Activity
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.O-teeosTarget: Arm's secure enclave that code isn't supposed to be able to jailbreakTarget: Arm's secure enclave that code isn't supposed to be able to jailbreakT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
I was reading the platform sources for the runtime and I found this peculiar
sys::cleanupimplementation on teeos (aarch64-unknown-teeos):rust/library/std/src/sys/pal/teeos/mod.rs
Lines 33 to 38 in 28e8a8c
This function is always invoked after
main. Theunsupported.rsimplementation is to just do nothing, but this is panicking instead. Even if it is somehow intentional, anrtabortcall would surely be much more appropriate in this context, given thatunimplementedinvolves a call to the global allocator and panic hook.It just looks wrong. Am I missing something?
@rustbot label T-libs O-teeos