[foreign-memaccess+abi] Integrated: 8268673: Stack walk across optimized entry frame on fresh native thread fails

Jorn Vernee jvernee at openjdk.java.net
Mon Jun 14 15:09:52 UTC 2021


On Mon, 14 Jun 2021 12:13:52 GMT, Jorn Vernee <jvernee at openjdk.org> wrote:

> Hi,
> 
> When native code creates a new thread and calls a Panama upcall, and during that upcall a stack walk is triggered, getting the sender frame for the entry frame is not possible, and should not be attempted.
> 
> For JNI this case is handled already by indicating the end of the stack frame stream, but for Panama upcalls it is not, and the VM will either hit an assert or crash when trying to find the last Java frame before the entry frame (which does not exist in this case).
> 
> This patch adds handling for panama upcalls frames to `frame::is_first_frame`, which is used by the stack walking code to determine when to stop walking.
> 
> Thanks,
> Jorn

This pull request has now been integrated.

Changeset: 2287ca5a
Author:    Jorn Vernee <jvernee at openjdk.org>
URL:       https://git.openjdk.java.net/panama-foreign/commit/2287ca5a530c348bc4ec7c0c6774e8ed9101dffa
Stats:     194 lines in 11 files changed: 193 ins; 0 del; 1 mod

8268673: Stack walk across optimized entry frame on fresh native thread fails

Reviewed-by: mcimadamore

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

PR: https://git.openjdk.java.net/panama-foreign/pull/558


More information about the panama-dev mailing list