RFR: 8261710: SA DSO objects have sizes that are too large [v5]

Serguei Spitsyn sspitsyn at openjdk.java.net
Sat Feb 20 09:57:40 UTC 2021


On Thu, 18 Feb 2021 02:56:55 GMT, Yasumasa Suenaga <ysuenaga at openjdk.org> wrote:

>> This PR relates to [JDK-8261702](https://bugs.openjdk.java.net/browse/JDK-8261702) ( #2562 )
>> 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 for executable code.
>
> Yasumasa Suenaga has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains seven commits:
> 
>  - Fix comments
>  - Merge remote-tracking branch 'upstream/master' into JDK-8261710
>  - Use p_filesz instead of p_memsz
>  - Remove unnecessary code
>  - Fix for OS X
>  - Use entire of address range of shared library
>  - 8261710: SA DSO objects have sizes that are too large

Marked as reviewed by sspitsyn (Reviewer).

-------------

PR: https://git.openjdk.java.net/jdk/pull/2563


More information about the serviceability-dev mailing list