JDK-4651918 : Core dump with non existing runlibrary
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.1
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2002-03-13
  • Updated: 2002-03-13
  • Resolved: 2002-03-13
Related Reports
Duplicate :  
JDK-4418494 - test nsk/regression/b4343963 crashes java_g VM
Relates :  
JDK-4343963 - hotspot dumps core on minor vm exits (e.g. mistyped library name)
Description
Test cases failed:
nsk/regression/b4343963

Build:       1.4.1-beta-b04
Platform:    solsparcv9
VM:          ClientVM/ServerVM
Mode:        comp/mixed/int
HotSpot Version: 
Java HotSpot(TM) Server VM 
(build 20020308105420.jmasa.baseline-fastdebug-debug, compiled mode)
How to reproduce:
cd /net/jano.sfbay/export/disk20/GammaBase/Bugs/<bug-id>
sh doit.sh

********Running With Week-ahead binary:
java version "1.4.1-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-beta-b04)
Java HotSpot(TM) Client VM (build 20020308105420.jmasa.baseline-fastdebug1-debug, mixed mode)
==> nsk/regression/b4343963 TEST log:
--> This test on #4343963 bug; Category: hotspot; Subcategory: runtime_system
    Synopsis: hotspot dumps core on minor vm exits (e.g. mistyped library name)

--> b4343963: TESTED_JAVA :
/net/alpheridies/export/VM/hopper/weekly/JDK/latest/solsparc/bin/java

--> b4343963: TESTED_JAVA version:
java version "1.4.1-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-beta-b04)
Java HotSpot(TM) Client VM (build 20020308105420.jmasa.baseline-fastdebug1-debug, mixed mode)

--> b4343963: Executing "TESTED_JAVA -XrunNoExistingLib -version" command...
Abort
--> b4343963: OutPut for -XrunNoExistingLib:
Error occurred during initialization of VM
Could not find -Xrun library: libNoExistingLib.so
Dumping core....

--> b4343963: FAILED: TESTED_JAVA dumps core for -XrunNoExistingLib

--> b4343963: Executing "TESTED_JAVA -Xms1 -version" command...
Abort
--> b4343963: OutPut for -Xms1:
Error occurred during initialization of VM
Too small initial heap
Dumping core....

--> b4343963: FAILED: TESTED_JAVA dumps core for -Xms1

--> b4343963: Executing "TESTED_JAVA -Xms1000000k -version" command...
Abort
--> b4343963: OutPut for -Xms1000000k:
Error occurred during initialization of VM
Incompatible initial and maximum heap sizes specified
Dumping core....

--> b4343963: FAILED: TESTED_JAVA dumps core for -Xms1000000k

--> b4343963: Executing "TESTED_JAVA -Xms1000000000k -Xmx1000000000k -version" command...
--> b4343963: OutPut for -Xms1000000000k -Xmx1000000000k:
Invalid initial heap size: -Xms1000000000k
Could not create the Java virtual machine.

--> b4343963: PASSED: TESTED_JAVA does not dump core for -Xms1000000000k -Xmx1000000000k

--> TESTED_JAVA dumps core for case(s) where a core dump not needed!
==> nsk/regression/b4343963 TEST FAILED
********Done Testing
Comments
EVALUATION Looks like a dup/not a bug based on bugID:4343963 Based on eval from bug mentioned above this is normal behavior. ###@###.### 2002-03-13 ###@###.### 2002-03-13 The core files occur only in the debug vm, and are desired as a debugging aid. The product vm does not generate a core file. Closing as a dup of 4418494. Note that the vm reported in the description *is* a debug vm, even though the command used to run it is java (not java_g). The vm is a so-called "fastdebug" vm which has debugging info but is also optimized to run tests faster. The version string in the vm gives a (non-obvious) indication that it is a debug vm: build 20020308105420.jmasa.baseline-fastdebug-debug,
11-06-2004