RFR: 8351842: Test issues on Windows with combination of --enable-linkable-runtime and --with-external-symbols-in-bundles=public

[Frederic Thevenet]

On Wed, 12 Mar 2025 20:00:29 GMT, Erik Joelsson <erikj at openjdk.org> wrote:

> What happens with the local debugging experience in the exploded image if you configure with ` --with-external-symbols-in-bundles=public`? Then the full debug symbols are only present in the *.full.pdb files. Will the debugger tools on Windows know automatically how to resolve that, or will this configuration be inconvenient for local dev/debug usecases? As I remember it, the current scheme was chosen to put the "full" pdb files as *.pdb in the exploded image whenever possible.

FWIW, from my work on https://github.com/openjdk/jdk/pull/16039 I remember verifying that debuggers on Windows do not rely on the filenames of pdb files to match the symbols and binaries, so AFAIK, the fact that the symbols for, say, `jvm.dll`, will be in a file named `jvm.dll.full.pdb` instead of `jvm.dll.pdb` does not imply it won't be found by the debugger (i.e. it used to be in a file named `jvm.pdb`)
Now, if I understand the proposed change correctly, the exploded image will contain two distinct `.pdb` files for each binaries, so a question remain about how a debugger might decide to choose one over the other, but do we know for sure that this indeed affect the right symbols to be picked up?

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

PR Comment: https://git.openjdk.org/jdk/pull/24012#issuecomment-2720726016