On Wed, 22 Oct 2025 18:05:09 GMT, Daniel Hu <[email protected]> wrote:
> I definitely agree that more testing could be done. I probably should've > figured this out before taking this task, but do you know how to build the > jdk deliberately with absolute paths? (or if you have any download links to > broken/incorrect jdk builds, that would also work). I did test the string > searching algorithm itself, by running the test code with existing string > patterns in the build files (e.g. "java") and the test successfully > failed/matched existing strings in a working jdk build. When I introduced this test it was together with this configure option `--disable-absolute-paths-in-output`. If you flip that to `enable`, that should cause native libraries to at least potentially contain absolute path references, though it may depend on the exact toolchain used. You should be able to check manually, without the test, by running something like: $ strings <path/to/lib> | grep <path/to/workspace> ------------- PR Comment: https://git.openjdk.org/jdk/pull/26030#issuecomment-3433988824
