JVM will crash, if it is not able to determine the current working directory.
Please see the following results with build 59c and with the build 63
<Result-b59c>
bash-3.00$ pwd
/home/rg157576/vittal
bash-3.00$ /net/sqindia.india/export/disk09/jdk/1.6.0/b59c//binaries/solsparc/bin/java -version
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current working directory.
at java.lang.System.initProperties(Native Method)
at java.lang.System.initializeSystemClass(System.java:1072)
<Result-b59c>
<Result-b63>
bash-3.00$ pwd
/home/rg157576/vittal
bash-3.00$ /net/sqindia.india/export/disk09/jdk/1.6.0/b63/binaries/solsparc/bin/java -version
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xff2aea90, pid=18142, tid=2
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-rc-b63 mixed mode)
# Problematic frame:
# C [libc.so.1+0x2ea90] strlen+0x50
#
# An error report file with more information is saved as /tmp/hs_err_pid18142.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Abort
</Result-b63>
Error report file is attached.
To reproduce
1. Create a directory say temp
2. move to temp
3. change temp permissions to 077 (Use other terminal)
4. Now run java -version.
In the above scenario jvm will fail to determine current directoy that leads to crash.
Please see the following results with build 59c and with the build 63
<Result-b59c>
bash-3.00$ pwd
/home/rg157576/vittal
bash-3.00$ /net/sqindia.india/export/disk09/jdk/1.6.0/b59c//binaries/solsparc/bin/java -version
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current working directory.
at java.lang.System.initProperties(Native Method)
at java.lang.System.initializeSystemClass(System.java:1072)
<Result-b59c>
<Result-b63>
bash-3.00$ pwd
/home/rg157576/vittal
bash-3.00$ /net/sqindia.india/export/disk09/jdk/1.6.0/b63/binaries/solsparc/bin/java -version
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xff2aea90, pid=18142, tid=2
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-rc-b63 mixed mode)
# Problematic frame:
# C [libc.so.1+0x2ea90] strlen+0x50
#
# An error report file with more information is saved as /tmp/hs_err_pid18142.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Abort
</Result-b63>
Error report file is attached.
To reproduce
1. Create a directory say temp
2. move to temp
3. change temp permissions to 077 (Use other terminal)
4. Now run java -version.
In the above scenario jvm will fail to determine current directoy that leads to crash.
- duplicates
-
JDK-6253381 -Xcheck:jni JNI call made with exception pending should be a warning
-
- Closed
-
- relates to
-
JDK-6361259 Java 1.6 MonitorExit clears exception thrown in native code
-
- Closed
-
-
JDK-6760147 java programs are not usable when current directory is unknown
-
- Closed
-