-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
UnwindManagedExceptionPass1 is failing on illumos amd64 #38373
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
@jasonbking suggested that if it is libunwind misbehaving, it would be helpful to come up with a short repro (preferably in plain C). @janvorli, is there any such repro available offhand? I am not sure whether to cut off the assembly stubs ( |
The behavior you are seeing is correct. Unhandled exception should exit via abort and it does so on Linux too. This is from my Ubuntu 16.04:
|
I was testing on Ubuntu 18.04. Although the exit code was 134, wasn't giving gcc -xc - <<EOF
#include <stdlib.h>
int main(void)
{
abort();
return (0);
}
EOF
./a.out
Aborted (core dumped) |
Ah, I was doing |
With a simple app that throws exception:
after the exception is rethrown and message is printed to stderr, application
abort()
s on SmartOS amd64.On Linux, it cleanly exits the process (without
abort()
).coredump inspection yields:
From libunwind, we hit this condition:
runtime/src/coreclr/src/pal/src/libunwind/src/x86_64/Gstep.c
Line 276 in 581dc19
then in UnwindManagedExceptionPass1, since we are at IP==0, we get here:
runtime/src/coreclr/src/vm/exceptionhandling.cpp
Line 4615 in 581dc19
stress trace looks like this:
The text was updated successfully, but these errors were encountered: