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

SA DSO objects have sizes that are too large

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P4
    • 17
    • 17
    • hotspot
    • None
    • b12

    Description

      When SA creates a DSO object, which is used to represent a shared object file (.so), it initializes the "size" to be the size of the shared object file. This usually results in the size being too big. This can cause SA to get confused about whether or not an address is in the shared object. SA should instead set the DSO's size to the amount of the file that is actually mapped.

      See JDK-8261702 for an example of an SA bug this bug caused (but was worked around).

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8248875 Umbrella bug for missing and broken SA features on OSX

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JDK-8261702 ClhsdbFindPC can fail due to PointerFinder incorrectly thinking an address is in a .so

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8263242 serviceability/sa/ClhsdbFindPC.java cannot find MaxJNILocalCapacity with ASLR

          • P3 - Major loss of function.
          • Resolved
          links to

          Commit Commit openjdk/jdk/3b350ad8

          Review Review openjdk/jdk/2563

          Activity

            People

              ysuenaga Yasumasa Suenaga
              cjplummer Chris Plummer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: