Grouped method entry events
Alan Bateman
Alan.Bateman at oracle.com
Sun Aug 7 15:52:30 UTC 2022
On 06/08/2022 10:18, Egor Ushakov wrote:
> Hi Chris,
>
> I was able to somewhat reproduce it with jdb:
> compile any simple samle app like
> public class A {
> public static void main(String[] args) {
> System.out.println("A"); // line 3
> }
> }
>
I tried this with JDK 11, 17 and 19 and don't see any significant
difference in the co-location. When you do "next" then JDI will get
events related to VM callout to checkPackageAccess. With JDK 11 I see 3
co-located events (2 entry, 1 exit) for the main thread. The libs code
has changed a bit since then and for JDK 17 and 19 there are 5
co-located events (4 entry, 1 exit). I don't recall seeing anything go
by that changed the code that decides if events are deferred. I think
Chris is right that if there was something was broken then there would
be test failures and bug reports. So I guess the question is whether the
co-location with this example does reflect what you are seeing or if
there is something else going on.
-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/serviceability-dev/attachments/20220807/6d829dbb/attachment.htm>
More information about the serviceability-dev
mailing list