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.
SeeJDK-8261702 for an example of an SA bug this bug caused (but was worked around).
See
- relates to
-
JDK-8248875 Umbrella bug for missing and broken SA features on OSX
-
- Open
-
-
JDK-8261702 ClhsdbFindPC can fail due to PointerFinder incorrectly thinking an address is in a .so
-
- Resolved
-
-
JDK-8263242 serviceability/sa/ClhsdbFindPC.java cannot find MaxJNILocalCapacity with ASLR
-
- Resolved
-