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

MaxJavaStackTraceDepth of zero is not handled correctly/consistently in the VM

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P4
    • 11
    • 7, 8, 9
    • hotspot
    • None
    • 6
    • b01
    • generic
    • generic

    Description

      On 22/06/2012 1:20 AM, Pierre Laporte wrote:
      > Hello Hotspot guys
      >
      > I have written a small web application to make the description of all
      > JVM options available (see http://jvm-options.tech.xebia.fr). To do so I
      > parsed the content of the globals.hpp file where options are defined.
      >
      > It seems though that the information in globals.hpp is not completely
      > true. A follower (@OlivierJaquemet) pointed that the
      > description of MaxJavaStackTraceDepth is slightly wrong :
      > "/Regarding options MaxJavaStackTraceDepth :
      > * With Java > 1.6, value 0 really means 0. value -1 or any negative
      > number must be specified to print all the stack (tested with 1.6.0_22,
      > 1.7.0 on Windows)
      > * With Java <= 1.5, value 0 means everything, JVM chokes on negative
      > number (tested with 1.5.0_22 on Windows)###@###.###
      > <mailto:###@###.###>/"
      >
      > As of jdk7u4, the description of this option in globals.hpp (line 2893)
      > is still "Max. no. of lines in the stack trace for Java exceptions (0
      > means all)". Can you update it with "Max. no. of lines in the stack
      > trace for Java exceptions (-1 means all, 0 means nothing)" ?
      >

      Attachments

        Issue Links

          Activity

            People

              coleenp Coleen Phillimore
              dholmes David Holmes
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: