On Tue, 19 May 2026 13:35:45 GMT, Kevin Walls <[email protected]> wrote:
> We could create a HotSpotCoreFileOrMiniDumpProvider, which would get its
> chance to open a (id, env) pair. But then I can't say if that is before or
> after the exising PID attempt, and whether that will be the same for
> everybody, or will change.
The Attach API was designed to allow for multiple providers. The intention was
that a provider throw AttachNotSupportedException if invoked to attach to
something that it doesn't recognize, then move on to try the next provider. The
existing provider should be throwing AttachNotSupportedException already if the
id is not a process ID. Can you confirm this is the case? I'd hate to see the
ambiguous case ("123" is both the PID of a live VM, and "123" is the core file)
to influence this.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/31011#issuecomment-4488399970
