RFR: 8313796: AsyncGetCallTrace crash on unreadable interpreter method pointer [v4]

[Johannes Bechberger]

On Tue, 8 Aug 2023 04:07:20 GMT, Erik Österlund <eosterlund at openjdk.org> wrote:

>> OK let's go with your suggestion, thanks for explaining. I'm actually skeptical this can actually be a non-null bad pointer, as we've only seen this crash happen once, and the pointer was null in that instance. But this solution looks robust, so thanks for suggesting it.
>
> So you can safely fetch something that might be a method, and even if it really is a method and that can be verified, it might be a concurrently unloading method that is about to get clobbered or uncommiyted. Dereferencing and using such a Method is also subject to occasional crashing. Might be a problem for another day though.

@fisk this might be solved in a new version of the API. I already spoke with @apangin about this and he's positive :)

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

PR Review Comment: https://git.openjdk.org/jdk/pull/15178#discussion_r1286647947