Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6799458

java -XX:HeapDumpPath= fubar produces segmentation fault

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: 6u11
    • Fix Version/s: None
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • CPU:
      x86
    • OS:
      solaris_2.5.1

      Description

      FULL PRODUCT VERSION :
      java version "1.6.0_11"
      Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
      Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode, sharing)


      ADDITIONAL OS VERSION INFORMATION :
      Linux baez.mi.oa-brera.inaf.it 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:12 EDT 2008 i686 i686 i386 GNU/Linux


      A DESCRIPTION OF THE PROBLEM :
      The command

      java -XX:HeapDumpPath= fubar

      (note the blank value for HeapDumpPath)

      produces a segmentation fault immediately. It would be a lot better if the JVM issued an error message complaining about the missing value.

      The segfault does *not* occur for JDK 1.6.0._07, which reports

      Exception in thread "main" java.lang.NoClassDefFoundError: fubar

      as it should. Even here, however, there is no complaint about the missing value for HeapDumpPath.


      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      java -XX:HeapDumpPath= fubar

      (or any class you prefer instead of the undefined "fubar")

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      "Error: missing value for argument XX:HeapDumpPath" or something similar.
      ACTUAL -
      Segmentation fault (core dumped)

      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      Segmentation fault (core dumped)

      REPRODUCIBILITY :
      This bug can be reproduced always.

      Release Regression From : 5.0u17
      The above release value was the last known release where this
      bug was not reproducible. Since then there has been a regression.

      Release Regression From : 5.0u17
      The above release value was the last known release where this
      bug was not reproducible. Since then there has been a regression.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dcubed Daniel Daugherty
                Reporter:
                ndcosta Nelson Dcosta (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: