On Tue, 30 Nov 2021 07:18:22 GMT, Thomas Stuefe <stu...@openjdk.org> wrote:

> This bypasses the currently observed problem, but we still have a 
> fundamentally unsafe mechanism in use here. :(

Definitely.  I think having some assert code that verifies that we don't do 
anything "unsafe" while in AsyncGetCallTrace might be a good enhancement, but 
the definition of "unsafe" in this case might be almost anything we do.

This change chops off a piece of the top of the iceberg as observed.  Thanks 
for all the code reviews.

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

PR: https://git.openjdk.java.net/jdk/pull/6606

Reply via email to