-
Bug
-
Resolution: Fixed
-
P2
-
hs21, 6u27
-
b17
-
generic, x86
-
generic, solaris_10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2212516 | 8 | Tom Rodriguez | P2 | Closed | Fixed | b01 |
| JDK-2211009 | 7 | Tom Rodriguez | P2 | Resolved | Fixed | b147 |
| JDK-2222890 | 6u34 | Poonam Bajaj Parhar | P2 | Closed | Fixed | b01 |
| JDK-2212517 | hs22 | Tom Rodriguez | P2 | Resolved | Fixed | b01 |
| JDK-2224176 | hs20.9 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | team |
Issue is reproducible with b145.
I was able to reproduce it with older bits (b125
The error message is not very informative:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x000000000000009a, pid=8508, tid=1100495168
#
# JRE version: 7.0-b145
# Java VM: Java HotSpot(TM) 64-Bit Server VM (21.0-b15-fastdebug mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C 0x000000000000009a
[error occurred during error reporting (printing problematic frame), id 0xb]
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
- backported by
-
JDK-2211009 VM crashes with SIGSEGV in compiled code
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-6961690 load oops from constant table on SPARC
-
- Closed
-