On Wed, 31 Aug 2022 00:25:20 GMT, Chris Plummer <[email protected]> wrote:
> There is a workaround we can do for > [JDK-8292217](https://bugs.openjdk.org/browse/JDK-8292217) for the use case > where a step over or step out is being done. This workaround can't be made to > also work for the step into case. From > [JDK-8292217](https://bugs.openjdk.org/browse/JDK-8292217) > > "There is a workaround that fixes this issue when doing a STEP_OVER or > STEP_OUT. Rather than the debug agent checking if it has enabled JVMTI single > stepping, instead it checks some fields in the ThreadNode that say if single > stepping is pending, and it is for a STEP_INTO. If it is not STEP_INTO, then > it can assume that no StepEvent will occur at the same location and therefor > the MethodEntryEvent should not be deferred. So this limits the bug to only > happening when doing a STEP_INTO. " This pull request has now been integrated. Changeset: 6ad151d0 Author: Chris Plummer <[email protected]> URL: https://git.openjdk.org/jdk/commit/6ad151d09623217699d3d21c36d4e01f3bfd7d7b Stats: 17 lines in 2 files changed: 10 ins; 0 del; 7 mod 8293143: Workaround for JDK-8292217 when doing "step over" of bytecode with unresolved cp reference Reviewed-by: sspitsyn, amenkov ------------- PR: https://git.openjdk.org/jdk/pull/10091
