To improve modularity and build time, move the declaration of the following
accessor from classfile/javaClasses.hpp to runtime/threadJavaClasses.hpp:
+ java_lang_Thread_FieldHolder
+ java_lang_Thread_Constants
+ java_lang_ThreadGroup
+ java_lang_VirtualThread
Also move javaThreadStatus.hpp from
On Fri, 5 Aug 2022 22:29:00 GMT, David Holmes wrote:
> Forward port JDK 19 -> JDK 20
This pull request has now been integrated.
Changeset: 87cda21c
Author:David Holmes
URL:
https://git.openjdk.org/jdk/commit/87cda21c5d85f6e6f628849b8670e2ecb4e105dd
Stats: 99 lines in 2 files cha
Forward port JDK 19 -> JDK 20
-
Commit messages:
- Merge remote-tracking branch 'jdk19/master' into Merge_jdk19
- 8290562: ThreadMXBean.getThread{Cpu,User}Time fails with -XX:-VMContinuations
The webrevs contain the adjustments done while merging with regards to each
parent branch
Hi Egor,
That is odd, and clearly wrong. It means that MethodEntryEvents are
being delivered when no longer even executing in the method. And you are
using the EVENT_THREAD suspend policy, so there should be a suspend for
each event. Offhand I can't think of any changes that would have caused
Hi,
we're experiencing strange grouping of method entry/exit events, is this
a bug or a feature?
We have one method entry request active with suspend policy 1 (suspend
thread).
important: we also have one active step request (step over)
In jdk 11 we have one composite event for each event, wh
On Mon, 1 Aug 2022 09:16:41 GMT, Alan Bateman wrote:
> ThreadMXBean.getThread{Cpu,User}Time is specified to return -1L when invoked
> with the id of a virtual thread. This isn't so when running with
> -XX:-VMContinuations (or ports without support for continuations in the VM)
> as it returns t
