Loading... (original) (raw)
When JVMTI's PopFrame removes a frame that was called via a call site that takes an appendix and that call site is reexecuted the appendix is not on the stack anymore because it got removed by the adapter. We need a way to push the appendix on the stack again before reexecution.
The bug manifests as:
assert(false) failed: DEBUG MESSAGE: MemberName required for invokeVirtual etc.
backported by
JDK-8023408 JSR 292: JVMTI PopFrame needs to handle appendix arguments
- Resolved
JDK-8034949 JSR 292: JVMTI PopFrame needs to handle appendix arguments
- Resolved
JDK-8035854 JSR 292: JVMTI PopFrame needs to handle appendix arguments
- Resolved
JDK-8057273 JSR 292: JVMTI PopFrame needs to handle appendix arguments
- Resolved
JDK-8035460 JSR 292: JVMTI PopFrame needs to handle appendix arguments
- Closed
JDK-8060840 JSR 292: JVMTI PopFrame needs to handle appendix arguments
- Closed
duplicates
JDK-8001076 Test testName=vm/mlvm/indy/func/jvmti/stepBreakPopReturn failing
- Closed
JDK-8009374 JSR292:assert(false) failed: DEBUG MESSAGE: MemberName required for invokeVirtual etc.
- Closed
relates to
JDK-8008511 JSR 292: MemberName vmtarget refs to methods must be updated at class redefinition
- Resolved
JDK-8024380 JSR-292: new internal contract between linker primitives and PopFrame is hard to support
- Open
JDK-8034935 JSR 292 support for PopFrame has a fragile coupling with DirectMethodHandle
- Resolved
(1 backported by, 2 duplicates, 3 relates to)