8254824: SignalHandlerMark have no purpose

Reviewed-by: stuefe, shade, dholmes, coleenp
This commit is contained in:
Robbin Ehn 2020-10-19 06:28:47 +00:00
parent 736e077335
commit 011dd0d8fa
11 changed files with 15 additions and 49 deletions

View file

@ -209,12 +209,11 @@ JVM_handle_linux_signal(int sig,
Thread* t = Thread::current_or_null_safe();
// Must do this before SignalHandlerMark, if crash protection installed we will longjmp away
// (no destructors can be run)
// If crash protection is installed we may longjmp away and no destructors
// for objects in this scope will be run.
// So don't use any RAII utilities before crash protection is checked.
os::ThreadCrashProtection::check_crash_protection(sig, t);
SignalHandlerMark shm(t);
// Note: it's not uncommon that JNI code uses signal/sigset to install
// then restore certain signal handler (e.g. to temporarily block SIGPIPE,
// or have a SIGILL handler when detecting CPU type). When that happens,