Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backtrace capture on SGX broken after (including) nightly-2023-11-20 #119806

Open
kostko opened this issue Jan 10, 2024 · 4 comments
Open

Backtrace capture on SGX broken after (including) nightly-2023-11-20 #119806

kostko opened this issue Jan 10, 2024 · 4 comments
Labels
C-bug Category: This is a bug. O-SGX Target: SGX P-medium Medium priority regression-untriaged Untriaged performance or correctness regression. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@kostko
Copy link

kostko commented Jan 10, 2024

It looks like that after #117895 (that seems to be the only SGX backtrace-related change between the two versions) enabling backtraces and attempting to capture one on the x86_64-fortanix-unknown-sgx target (sometimes) results in the enclave hanging.

Code

Unfortunately I don't currently have a minimal reproducer example, but roughly:

std::env::set_var("RUST_BACKTRACE", "1");
// ... unspecified logic, multiple nested frames ...
std::backtrace::Backtrace::capture();

I expected to see this happen: backtrace is captured without issues.

Instead, this happened: the Backtrace::capture() method appears to hang.

Version it worked on

It most recently worked on: nightly-2023-11-19

Version with regression

nightly-2023-11-20

@kostko kostko added C-bug Category: This is a bug. regression-untriaged Untriaged performance or correctness regression. labels Jan 10, 2024
@rustbot rustbot added I-prioritize Issue: Indicates that prioritization has been requested for this issue. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Jan 10, 2024
@Nilstrieb
Copy link
Member

cc @mzohreva

@Nilstrieb Nilstrieb added O-SGX Target: SGX and removed needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Jan 10, 2024
@Nilstrieb
Copy link
Member

also @raoulstrackx @jethrogb as the other SGX maintainers

@apiraino
Copy link
Contributor

apiraino commented Feb 1, 2024

WG-prioritization assigning priority (Zulip discussion).

@rustbot label -I-prioritize +P-medium

@rustbot rustbot added P-medium Medium priority and removed I-prioritize Issue: Indicates that prioritization has been requested for this issue. labels Feb 1, 2024
@apiraino apiraino added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Feb 1, 2024
@BelalH
Copy link

BelalH commented Feb 9, 2024

Hello,
I am Belal Haikal an engineering manager at Fortanix, also colleague of Raoul and Jethro who were mentioned in a previous comment.
my team tried to reproduce the issue however we couldn't trigger the expected fault
is there a test service we can run to reproduce the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. O-SGX Target: SGX P-medium Medium priority regression-untriaged Untriaged performance or correctness regression. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants