| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8206684 | 11.0.1 | Zhengyu Gu | P2 | Resolved | Fixed | b01 |
| JDK-8206185 | 11 | Zhengyu Gu | P2 | Resolved | Fixed | b21 |
| JDK-8214610 | 8u211 | Zhengyu Gu | P2 | Resolved | Fixed | b01 |
| JDK-8210933 | 8u202 | Zhengyu Gu | P2 | Closed | Fixed | b01 |
| JDK-8220863 | emb-8u211 | Zhengyu Gu | P2 | Resolved | Fixed | master |
const NativeCallStack NativeCallStack::EMPTY_STACK(0, false);
But it's written to here:
// Construct NativeCallStack::EMPTY_STACK. It may get constructed twice,
// but it is benign, the results are the same.
::new ((void*)&NativeCallStack::EMPTY_STACK) NativeCallStack(0, false);
Writing to a const global is catch-on-fire and it appears that when recent clangs (>= clang-6.0) compile this, EMPTY_STACK is placed in read-only storage, resulting in SIGSEGV.
- backported by
-
JDK-8206185 SIGSEGV on write to NativeCallStack::EMPTY_STACK
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-8055007 NMT2: emptyStack missing in minimal build
-
- Closed
-
-
JDK-8206183 Possible construct EMPTY_STACK and allocation stack, etc. on first use.
-
- Resolved
-