RFR: 8316309: AArch64: VMError::print_native_stack() crashes on Java native method frame [v2]
Patricio Chilano Mateo
pchilanomate at openjdk.org
Tue Oct 3 19:32:39 UTC 2023
On Tue, 3 Oct 2023 07:36:22 GMT, David Holmes <dholmes at openjdk.org> wrote:
>> The second part of the condition includes the previous checks for is_compiled_frame(), is_native_frame(), is_runtime_frame() plus any other frame that would use sender_for_compiled_frame() when calling frame::sender(), like the safepoint stub.
>
> So what is left that is not covered by that condition? Just wondering if there is a simpler form that makes it somewhat clearer what this actually tests for as the old condition was easily understandable and the new one is obscure.
The entry frame and upcall stub frame cases, which do not expect a call to frame::sender() unless there are more frames to walk (see those respective cases in frame::sender_raw()). The native frame case. And then I guess all cases where we crash in some stub routine where the pc belongs to the CodeCache but doesn't match any particular frame (interpreter, compiled, runtime stub, etc), like if we crash in the generate_cont_thaw() stub.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/15972#discussion_r1344625821
More information about the hotspot-dev
mailing list