My Oracle Support Banner

JDB ClassExclusionFilter Stops in Wrong Method when Method References Used (Doc ID 2502349.1)

Last updated on OCTOBER 24, 2019

Applies to:

Java SE JDK and JRE - Version 8 and later
Information in this document applies to any platform.

Symptoms

  

Disclaimer: The code samples and file names used in this article represent fictitious sample names that make up an example. Any similarity to actual code is purely coincidental and not intended in any other manner.

  

With method references, JDK does not allow the JDB debugger's classExclusionFilter to stop where expected when the extra stepping filter jdk.internal.* is used.

Consider the following test code:


7. Notice the debugger stops at my.stepping.StepIntoMethodRef.lambda$actualMethod$0(), line=13
  However, it should have stopped at line 10.




Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.