-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
SIGILL from InitializeOpenSSLShim on alpine arm64 during lldb debugging #103887
Comments
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
For OpenSSL this is "normal". Based on the stack, You can do |
Here is where OpenSSL does that probing. It installs a SIGILL handler to test for available CPU features. https://github.com/openssl/openssl/blob/89c9c3b857b5d68d835c3c3d371dc74a26f568fd/crypto/armcap.c#L368 since you are running under a debugger, you are getting a "first chance" error for the SIGILL. |
Thanks @vcsjones! After the export, I don't see SIGILL anymore. 👍 |
(ran into it while debugging an unrelated nuget issue dotnet/diagnostics#4753)
On linux-musl-arm64,
apk add lldb openssl-dbg
anddotnet tool install -g dotnet-sos && dotnet-sos install
, runningdotnet build
under lldb reveals a (non-fatal) SIGILL:continuing (with
c
command) a few times continues the debugging.cc @wfurt, @janvorli might be that there is nothing actionable for us.
The text was updated successfully, but these errors were encountered: