8248876: LoadObject with bad base address created for exec file on linux

[ktakakuri]

I would like to backport
8248876: LoadObject with bad base address created for exec file on linux.

The original patch does not apply cleanly to 8u, and this is a clean backport from 11u.

Testing:
build on Linux x86_64
tier1 on Linux x86_64

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8248876: LoadObject with bad base address created for exec file on linux

Reviewers

• Paul Hohensee (@phohensee - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk8u-dev pull/47/head:pull/47
$ git checkout pull/47

Update a local copy of the PR:
$ git checkout pull/47
$ git pull https://git.openjdk.java.net/jdk8u-dev pull/47/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 47

View PR using the GUI difftool:
$ git pr show -t 47

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk8u-dev/pull/47.diff

[bridgekeeper]

👋 Welcome back ktakakuri! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (d0b16f00)

[ktakakuri]

Could anyone review this backport please?

[phohensee]

/clean

[phohensee]

Confirmed the backport from 11u is clean.

[openjdk]

@ktakakuri This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8248876: LoadObject with bad base address created for exec file on linux

Reviewed-by: phh

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 37 new commits pushed to the master branch:

• 680b09c: 8168926: C2: Bytecode escape analyzer crashes due to stack overflow
• 51f69d9: 8221988: add possibility to build with Visual Studio 2019
• 1b3e8ea: 8170530: bash configure output contains a typo in a suggested library name
• 1067c54: 8235211: serviceability/attach/RemovingUnixDomainSocketTest.java fails with AttachNotSupportedException: Unable to open socket file
• 1bc3be2: Merge
• ee82a7d: 8282458: Update .jcheck/conf file for 8u move to git
• d91ee59: Added tag jdk8u332-ga for changeset 37aca7715d13
• 607b14e: 8285445: cannot open file "NUL:"
• 62defc3: 8284772: 8u GHA: Use GCC Major Version Dependencies Only
• 65c4a5d: Merge
• ... and 27 more: https://git.openjdk.java.net/jdk8u-dev/compare/10029f784ef7be458a7b6ff3cc21649ff0abb6f3...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

@phohensee This backport pull request is now marked as clean

[phohensee]

Pref-submit build failures appear to be due to incompatible compilers.

[ktakakuri]

@phohensee
Thank you for your review.
I am not sure if I should continue to integrate.
Is there any other work that needs to be done?

[phohensee]

Yes. You need to tag the JBS issue with 'jdk8u-fix-request' and wait for a maintainer to approve it by adding the 'jdk8u-fix-yes' tag. Once that's done, you can integrate it. I'll sponsor if you like.

[ktakakuri]

/integrate

[openjdk]

@ktakakuri
Your change (at version d0b16f0) is now ready to be sponsored by a Committer.

[phohensee]

/sponsor

Got the approval. Presubmit failures appear to be an infrastructure problem.

[openjdk]

Going to push as commit 3e0eb09.
Since your change was applied there have been 38 commits pushed to the master branch:

• 6b94b65: 8278138: OpenJDK8 fails to start on Windows 8.1 after upgrading compiler to VS2017
• 680b09c: 8168926: C2: Bytecode escape analyzer crashes due to stack overflow
• 51f69d9: 8221988: add possibility to build with Visual Studio 2019
• 1b3e8ea: 8170530: bash configure output contains a typo in a suggested library name
• 1067c54: 8235211: serviceability/attach/RemovingUnixDomainSocketTest.java fails with AttachNotSupportedException: Unable to open socket file
• 1bc3be2: Merge
• ee82a7d: 8282458: Update .jcheck/conf file for 8u move to git
• d91ee59: Added tag jdk8u332-ga for changeset 37aca7715d13
• 607b14e: 8285445: cannot open file "NUL:"
• 62defc3: 8284772: 8u GHA: Use GCC Major Version Dependencies Only
• ... and 28 more: https://git.openjdk.java.net/jdk8u-dev/compare/10029f784ef7be458a7b6ff3cc21649ff0abb6f3...master

Your commit was automatically rebased without conflicts.

[openjdk]

@phohensee @ktakakuri Pushed as commit 3e0eb09.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

[gnu-andrew]

/sponsor

Got the approval. Presubmit failures appear to be an infrastructure problem.

This has been fixed by JDK-8284772 for some time. For future such PRs, I'd suggest a rebase so the tests are re-run.