Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2041217 | 1.4.0 | Hui Huang | P2 | Closed | Fixed | beta |
Mode: -Xmixed, -Xcomp, -Xint
Platform : Linux
Steps to reproduce:
1. Point JAVA_HOME to the latest promoted jdk1.4 linux binaries
2. ${JAVA_HOME}/bin/java_g -server -version
Output:
[tester@nanobug ~]$ $JAVA_HOME/bin/java_g -server -version
java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b54)
Java HotSpot(TM) Server VM (build 1.4beta-B54-debug, mixed mode)
Segmentation fault
[tester@nanobug ~]$
Note: This seems to happen very intermittently with Server VM as well as Client VM. We observed it with both -Xmixed and -Xint modes.
**************************************************************
Still java -version throws Segmentation Fault in Linux with build 57 and specially on roborooter { version 7.0.91) it provides following output
Steps to reproduce
1) rlogin to roborooter
2) cd /net/jdk/export/disk8/local.java/jdk1.4/linux-i386/bin
3)./java -version
Output:
[tester@roborooter bin]$ ./java -version
Unexpected Signal : 11 occurred at PC=0x402378BF
Function=start_thread__2osP6Thread+0x33
Library=/.automount/jdk.eng/root/export/disk6/promoted/jdk/1.4/beta/b57/binaries/linux-i386/jre/lib/i386/client/libjvm.so
Current Java thread:
Segmentation fault
satheesh.pothuganti@eng 2001-03-29
-----------------------------------
also seen in ladybird. only happens in java_g, not reproducible with java.
it doesn't matter if I use "-Xcomp" or not, but it seems to happen more
frequently with "-Xcomp":
saw:~> repeat 500 java_g -Xcomp -version
... (after about 30 iterations) ...
java version "1.3.1-rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc1-b20)
Java HotSpot(TM) Client VM (build 1.3.1-internal-debug, compiled mode)
java version "1.3.1-rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc1-b20)
Java HotSpot(TM) Client VM (build 1.3.1-internal-debug, compiled mode)
****************
Another exception has been detected while we were handling last error.
Dumping information about last error:
ERROR REPORT FILE = (N/A)
PC = 0x0x4aa51ba8
SIGNAL = 11
FUNCTION NAME = (N/A)
LIBRARY NAME = (N/A)
Please check ERROR REPORT FILE for further information, if there is any.
Good bye.
hui.huang@Eng 2001-04-08
-------------------------------------
This turns out to be that my workspace was somehow corrupted. After destroy
the old workspace and completely rebuild it with latest ladybird tree, I
cannot reproduce the crash with "repeat 500 java_g -version". What a
Saturday night.
hui.huang@Eng 2001-04-08
Platform : Linux
Steps to reproduce:
1. Point JAVA_HOME to the latest promoted jdk1.4 linux binaries
2. ${JAVA_HOME}/bin/java_g -server -version
Output:
[tester@nanobug ~]$ $JAVA_HOME/bin/java_g -server -version
java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b54)
Java HotSpot(TM) Server VM (build 1.4beta-B54-debug, mixed mode)
Segmentation fault
[tester@nanobug ~]$
Note: This seems to happen very intermittently with Server VM as well as Client VM. We observed it with both -Xmixed and -Xint modes.
**************************************************************
Still java -version throws Segmentation Fault in Linux with build 57 and specially on roborooter { version 7.0.91) it provides following output
Steps to reproduce
1) rlogin to roborooter
2) cd /net/jdk/export/disk8/local.java/jdk1.4/linux-i386/bin
3)./java -version
Output:
[tester@roborooter bin]$ ./java -version
Unexpected Signal : 11 occurred at PC=0x402378BF
Function=start_thread__2osP6Thread+0x33
Library=/.automount/jdk.eng/root/export/disk6/promoted/jdk/1.4/beta/b57/binaries/linux-i386/jre/lib/i386/client/libjvm.so
Current Java thread:
Segmentation fault
satheesh.pothuganti@eng 2001-03-29
-----------------------------------
also seen in ladybird. only happens in java_g, not reproducible with java.
it doesn't matter if I use "-Xcomp" or not, but it seems to happen more
frequently with "-Xcomp":
saw:~> repeat 500 java_g -Xcomp -version
... (after about 30 iterations) ...
java version "1.3.1-rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc1-b20)
Java HotSpot(TM) Client VM (build 1.3.1-internal-debug, compiled mode)
java version "1.3.1-rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc1-b20)
Java HotSpot(TM) Client VM (build 1.3.1-internal-debug, compiled mode)
****************
Another exception has been detected while we were handling last error.
Dumping information about last error:
ERROR REPORT FILE = (N/A)
PC = 0x0x4aa51ba8
SIGNAL = 11
FUNCTION NAME = (N/A)
LIBRARY NAME = (N/A)
Please check ERROR REPORT FILE for further information, if there is any.
Good bye.
hui.huang@Eng 2001-04-08
-------------------------------------
This turns out to be that my workspace was somehow corrupted. After destroy
the old workspace and completely rebuild it with latest ladybird tree, I
cannot reproduce the crash with "repeat 500 java_g -version". What a
Saturday night.
hui.huang@Eng 2001-04-08
- backported by
-
JDK-2041217 java_g -version throws Segmentation Fault in Linux
-
- Closed
-
- duplicates
-
JDK-4446632 java -version never terminates on Linux RedHat 6.2 Single kernel mode
-
- Closed
-
-
JDK-4450578 'java -version' causes system hang & cpu usage jumps to 90% on Linux with 1.4b60
-
- Closed
-
-
JDK-4456715 Linux: intermittent hotspot message when VM exits
-
- Closed
-
- relates to
-
JDK-4436291 java -version hangs on few linux machines using b59
-
- Closed
-
-
JDK-4423824 SEGV on vm exit - intermittent/timing related
-
- Closed
-
(1 relates to)