i.e. on the same BCI have two different labels and two different stack frames. I don't know how this is handled in ASM, but apparently it's only starting to become a problem with the JDK ClassFile API ...

The default stacking walking in async-profiler, Frame Pointer (FP) stack walking, is a technique for collecting call stacks by tracking frame pointers in memory. Each function call maintains a pointer ...