RFC (csr): 8225142: JVMTI spec incorrectly states that PopFrame can not be called on the current thread

[David Holmes]

Hi Serguei,

Sorry but I'm rather confused - what does it mean to do a "popframe" on 
the current thread? The whole point of popframe is to suspend a target 
thread when it is executing a specific method, and then call popframe to 
"back up" the thread to the point where it will call that method again 
when resumed. How does that work with the current thread?

Thanks,
David

On 1/06/2019 1:59 pm, serguei.spitsyn at oracle.com wrote:
> Hi All,
> 
> Please comment or.and review the following CSR.
> 
> The CSR:
> https://bugs.openjdk.java.net/browse/JDK-8225142
> 
> The bug:
> https://bugs.openjdk.java.net/browse/JDK-8205126
> 
> Updated JVMTI spec:
> http://cr.openjdk.java.net/~sspitsyn/webrevs/2019/8205126-jvmti-spec-popframe.1/jvmti.html
> 
> 
> Specdiff:
> http://cr.openjdk.java.net/~sspitsyn/webrevs/2019/8205126-jvmti-spec-popframe.1/jvmti-specdiff/
> 
> 
> Summary:
>    The JVMTI PopFrame() spec does not match the implementation.
>    It says the  specified thread can not be the current thread.
>    The fix aligns:
>     - spec with implementaion
>     - PopFrame spec with ForceEarlyReturn spec
> 
> Thanks,
> Serguei