8372759: Test build/AbsPathsInImage.java fails after JDK-8370438

[MBaesken]

Fei Yang reported this test error on a Debian GNU/Linux 13 (trixie) x86_64 machine:

$ make test TEST="test/jdk/build/AbsPathsInImage.java"

STDERR:
java.lang.Exception: Test failed
        at AbsPathsInImage.main(AbsPathsInImage.java:132)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
        at java.base/java.lang.reflect.Method.invoke(Method.java:565)
        at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
        at java.base/java.lang.Thread.run(Thread.java:1516)

The lto - built libsplashscreen.so was report to cause this.
To get rid of the unwanted paths in the shared lib (or in debug info files) we should not only compile but also link with debug prefix settings.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8372759: Test build/AbsPathsInImage.java fails after JDK-8370438 (Bug - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28676/head:pull/28676
$ git checkout pull/28676

Update a local copy of the PR:
$ git checkout pull/28676
$ git pull https://git.openjdk.org/jdk.git pull/28676/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28676

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28676.diff

[bridgekeeper]

👋 Welcome back mbaesken! 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 change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

@MBaesken The following label will be automatically applied to this pull request:

• build

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.