CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
Dan and Chris

Could one of you, please, review the CSR for 8187289:
  https://bugs-stage.openjdk.java.net/browse/JDK-8191098

Bug is:
  https://bugs-stage.openjdk.java.net/browse/JDK-8187289

Approved webrev:
  http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/


This CSR covers a change in behavior, not in the JVMTI spec.
We decided that the JVMTI NotifyFramePop is intuitive enough and does not need an update.

Thanks,
Serguei


 
Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

Chris Plummer
Hi Serguei,

I've read through it and it looks fine except for one minor thing:

"The solution is to clear all bound NotifyFramePop requests when a stack frame is popped."

I think this could be made more clear. It makes it sound like you clear *all* NotifyFramePop requests the first time *any* frame is popped.

This is the first time I've dealt with a CSR. What do I need to do to mark it reviewed?

thanks,

Chris

On 11/16/17 4:25 PM, [hidden email] wrote:
Dan and Chris

Could one of you, please, review the CSR for 8187289:
  https://bugs-stage.openjdk.java.net/browse/JDK-8191098

Bug is:
  https://bugs-stage.openjdk.java.net/browse/JDK-8187289

Approved webrev:
  http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/


This CSR covers a change in behavior, not in the JVMTI spec.
We decided that the JVMTI NotifyFramePop is intuitive enough and does not need an update.

Thanks,
Serguei


 


Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
Hi Chris,

Thank you a lot for looking at the CSR.


On 11/16/17 16:34, Chris Plummer wrote:
Hi Serguei,

I've read through it and it looks fine except for one minor thing:

"The solution is to clear all bound NotifyFramePop requests when a stack frame is popped."

I think this could be made more clear. It makes it sound like you clear *all* NotifyFramePop requests the first time *any* frame is popped.


I've changed it to:
  "The solution is to clear the NotifyFramePop requests related to the popped frame when a stack frame is popped."

Does is sound better?


This is the first time I've dealt with a CSR. What do I need to do to mark it reviewed?

It is the first time for me too. :)
I think, you have to add yourself to the reviewed-by list.
I've just added you to this list.
Also, it could be Ok to add comments.

Thanks,
Serguei




thanks,

Chris

On 11/16/17 4:25 PM, [hidden email] wrote:
Dan and Chris

Could one of you, please, review the CSR for 8187289:
  https://bugs-stage.openjdk.java.net/browse/JDK-8191098

Bug is:
  https://bugs-stage.openjdk.java.net/browse/JDK-8187289

Approved webrev:
  http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/


This CSR covers a change in behavior, not in the JVMTI spec.
We decided that the JVMTI NotifyFramePop is intuitive enough and does not need an update.

Thanks,
Serguei


 



Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
Chris,

I've also moved the statements about compatibility risk from the "Description" section
to the "Compatibility Risk Description" special section.

Thanks,
Serguei


On 11/16/17 16:56, [hidden email] wrote:
Hi Chris,

Thank you a lot for looking at the CSR.


On 11/16/17 16:34, Chris Plummer wrote:
Hi Serguei,

I've read through it and it looks fine except for one minor thing:

"The solution is to clear all bound NotifyFramePop requests when a stack frame is popped."

I think this could be made more clear. It makes it sound like you clear *all* NotifyFramePop requests the first time *any* frame is popped.


I've changed it to:
  "The solution is to clear the NotifyFramePop requests related to the popped frame when a stack frame is popped."

Does is sound better?


This is the first time I've dealt with a CSR. What do I need to do to mark it reviewed?

It is the first time for me too. :)
I think, you have to add yourself to the reviewed-by list.
I've just added you to this list.
Also, it could be Ok to add comments.

Thanks,
Serguei




thanks,

Chris

On 11/16/17 4:25 PM, [hidden email] wrote:
Dan and Chris

Could one of you, please, review the CSR for 8187289:
  https://bugs-stage.openjdk.java.net/browse/JDK-8191098

Bug is:
  https://bugs-stage.openjdk.java.net/browse/JDK-8187289

Approved webrev:
  http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/


This CSR covers a change in behavior, not in the JVMTI spec.
We decided that the JVMTI NotifyFramePop is intuitive enough and does not need an update.

Thanks,
Serguei


 




Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

Daniel D. Daugherty
Also reviewed the CSR.

Added a comment about one typo/grammar change, but it's
finalized so I did not actually make the change.

Dan


On 11/16/17 8:01 PM, [hidden email] wrote:
Chris,

I've also moved the statements about compatibility risk from the "Description" section
to the "Compatibility Risk Description" special section.

Thanks,
Serguei


On 11/16/17 16:56, [hidden email] wrote:
Hi Chris,

Thank you a lot for looking at the CSR.


On 11/16/17 16:34, Chris Plummer wrote:
Hi Serguei,

I've read through it and it looks fine except for one minor thing:

"The solution is to clear all bound NotifyFramePop requests when a stack frame is popped."

I think this could be made more clear. It makes it sound like you clear *all* NotifyFramePop requests the first time *any* frame is popped.


I've changed it to:
  "The solution is to clear the NotifyFramePop requests related to the popped frame when a stack frame is popped."

Does is sound better?


This is the first time I've dealt with a CSR. What do I need to do to mark it reviewed?

It is the first time for me too. :)
I think, you have to add yourself to the reviewed-by list.
I've just added you to this list.
Also, it could be Ok to add comments.

Thanks,
Serguei




thanks,

Chris

On 11/16/17 4:25 PM, [hidden email] wrote:
Dan and Chris

Could one of you, please, review the CSR for 8187289:
  https://bugs-stage.openjdk.java.net/browse/JDK-8191098

Bug is:
  https://bugs-stage.openjdk.java.net/browse/JDK-8187289

Approved webrev:
  http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/


This CSR covers a change in behavior, not in the JVMTI spec.
We decided that the JVMTI NotifyFramePop is intuitive enough and does not need an update.

Thanks,
Serguei


 





Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
Thanks a lot, Dan.
I've made the suggested change.

Thanks,
Serguei



On 11/16/17 17:27, Daniel D. Daugherty wrote:
Also reviewed the CSR.

Added a comment about one typo/grammar change, but it's
finalized so I did not actually make the change.

Dan


On 11/16/17 8:01 PM, [hidden email] wrote:
Chris,

I've also moved the statements about compatibility risk from the "Description" section
to the "Compatibility Risk Description" special section.

Thanks,
Serguei


On 11/16/17 16:56, [hidden email] wrote:
Hi Chris,

Thank you a lot for looking at the CSR.


On 11/16/17 16:34, Chris Plummer wrote:
Hi Serguei,

I've read through it and it looks fine except for one minor thing:

"The solution is to clear all bound NotifyFramePop requests when a stack frame is popped."

I think this could be made more clear. It makes it sound like you clear *all* NotifyFramePop requests the first time *any* frame is popped.


I've changed it to:
  "The solution is to clear the NotifyFramePop requests related to the popped frame when a stack frame is popped."

Does is sound better?


This is the first time I've dealt with a CSR. What do I need to do to mark it reviewed?

It is the first time for me too. :)
I think, you have to add yourself to the reviewed-by list.
I've just added you to this list.
Also, it could be Ok to add comments.

Thanks,
Serguei




thanks,

Chris

On 11/16/17 4:25 PM, [hidden email] wrote:
Dan and Chris

Could one of you, please, review the CSR for 8187289:
  https://bugs-stage.openjdk.java.net/browse/JDK-8191098

Bug is:
  https://bugs-stage.openjdk.java.net/browse/JDK-8187289

Approved webrev:
  http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/


This CSR covers a change in behavior, not in the JVMTI spec.
We decided that the JVMTI NotifyFramePop is intuitive enough and does not need an update.

Thanks,
Serguei


 






Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

David Holmes
In reply to this post by serguei.spitsyn@oracle.com
On 17/11/2017 10:25 AM, [hidden email] wrote:
> Dan and Chris
>
> Could one of you, please, review the CSR for 8187289:
> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>
> Bug is:
> https://bugs-stage.openjdk.java.net/browse/JDK-8187289

The links above should not be to bugs-stage!

David

> Approved webrev:
> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/
>
>
> This CSR covers a change in behavior, not in the JVMTI spec.
> We decided that the JVMTI NotifyFramePop is intuitive enough and does
> not need an update.
>
> Thanks,
> Serguei
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

David Holmes
The CSR needs to be created again from the real bug report. Everyone
will need to re-review and re-add any necessary comments.

David

On 17/11/2017 11:51 AM, David Holmes wrote:

> On 17/11/2017 10:25 AM, [hidden email] wrote:
>> Dan and Chris
>>
>> Could one of you, please, review the CSR for 8187289:
>> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>>
>> Bug is:
>> https://bugs-stage.openjdk.java.net/browse/JDK-8187289
>
> The links above should not be to bugs-stage!
>
> David
>
>> Approved webrev:
>> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/ 
>>
>>
>>
>> This CSR covers a change in behavior, not in the JVMTI spec.
>> We decided that the JVMTI NotifyFramePop is intuitive enough and does
>> not need an update.
>>
>> Thanks,
>> Serguei
>>
>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
Hi David,

I've to leave now for a couple of hours.
I've created the CSR from the real bug report, but don't know anything
about the bugs-stage.
A link "csr for" was auto-added when the CSR was created.

Thanks,
Serguei


On 11/16/17 17:53, David Holmes wrote:

> The CSR needs to be created again from the real bug report. Everyone
> will need to re-review and re-add any necessary comments.
>
> David
>
> On 17/11/2017 11:51 AM, David Holmes wrote:
>> On 17/11/2017 10:25 AM, [hidden email] wrote:
>>> Dan and Chris
>>>
>>> Could one of you, please, review the CSR for 8187289:
>>> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>>>
>>> Bug is:
>>> https://bugs-stage.openjdk.java.net/browse/JDK-8187289
>>
>> The links above should not be to bugs-stage!
>>
>> David
>>
>>> Approved webrev:
>>> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/ 
>>>
>>>
>>>
>>> This CSR covers a change in behavior, not in the JVMTI spec.
>>> We decided that the JVMTI NotifyFramePop is intuitive enough and
>>> does not need an update.
>>>
>>> Thanks,
>>> Serguei
>>>
>>>
>>>

Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

David Holmes
On 17/11/2017 12:00 PM, [hidden email] wrote:
> Hi David,
>
> I've to leave now for a couple of hours.
> I've created the CSR from the real bug report, but don't know anything
> about the bugs-stage.
> A link "csr for" was auto-added when the CSR was created.

You must have done that while looking at the bug on bugs-stage. The real
bug:

https://bugs.openjdk.java.net/browse/JDK-8187289

has no CSR.

David

> Thanks,
> Serguei
>
>
> On 11/16/17 17:53, David Holmes wrote:
>> The CSR needs to be created again from the real bug report. Everyone
>> will need to re-review and re-add any necessary comments.
>>
>> David
>>
>> On 17/11/2017 11:51 AM, David Holmes wrote:
>>> On 17/11/2017 10:25 AM, [hidden email] wrote:
>>>> Dan and Chris
>>>>
>>>> Could one of you, please, review the CSR for 8187289:
>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>>>>
>>>> Bug is:
>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8187289
>>>
>>> The links above should not be to bugs-stage!
>>>
>>> David
>>>
>>>> Approved webrev:
>>>> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/ 
>>>>
>>>>
>>>>
>>>> This CSR covers a change in behavior, not in the JVMTI spec.
>>>> We decided that the JVMTI NotifyFramePop is intuitive enough and
>>>> does not need an update.
>>>>
>>>> Thanks,
>>>> Serguei
>>>>
>>>>
>>>>
>
Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
On 11/16/17 18:23, David Holmes wrote:
> On 17/11/2017 12:00 PM, [hidden email] wrote:
>> Hi David,
>>
>> I've to leave now for a couple of hours.
>> I've created the CSR from the real bug report, but don't know
>> anything about the bugs-stage.
>> A link "csr for" was auto-added when the CSR was created.
>
> You must have done that while looking at the bug on bugs-stage.

Most likely.
But it is unclear how I've got there. :(


> The real bug:
>
> https://bugs.openjdk.java.net/browse/JDK-8187289

Ok.
I'll create the CSR once more.
Thank you for catching this problem, David!

Thanks,
Serguei


> has no CSR.
>
> David
>
>> Thanks,
>> Serguei
>>
>>
>> On 11/16/17 17:53, David Holmes wrote:
>>> The CSR needs to be created again from the real bug report. Everyone
>>> will need to re-review and re-add any necessary comments.
>>>
>>> David
>>>
>>> On 17/11/2017 11:51 AM, David Holmes wrote:
>>>> On 17/11/2017 10:25 AM, [hidden email] wrote:
>>>>> Dan and Chris
>>>>>
>>>>> Could one of you, please, review the CSR for 8187289:
>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>>>>>
>>>>> Bug is:
>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8187289
>>>>
>>>> The links above should not be to bugs-stage!
>>>>
>>>> David
>>>>
>>>>> Approved webrev:
>>>>> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/ 
>>>>>
>>>>>
>>>>>
>>>>> This CSR covers a change in behavior, not in the JVMTI spec.
>>>>> We decided that the JVMTI NotifyFramePop is intuitive enough and
>>>>> does not need an update.
>>>>>
>>>>> Thanks,
>>>>> Serguei
>>>>>
>>>>>
>>>>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
On 11/16/17 21:40, [hidden email] wrote:

> On 11/16/17 18:23, David Holmes wrote:
>> On 17/11/2017 12:00 PM, [hidden email] wrote:
>>> Hi David,
>>>
>>> I've to leave now for a couple of hours.
>>> I've created the CSR from the real bug report, but don't know
>>> anything about the bugs-stage.
>>> A link "csr for" was auto-added when the CSR was created.
>>
>> You must have done that while looking at the bug on bugs-stage.
>
> Most likely.
> But it is unclear how I've got there. :(
>
>
>> The real bug:
>>
>> https://bugs.openjdk.java.net/browse/JDK-8187289
>
> Ok.
> I'll create the CSR once more.

The CSR is:
   https://bugs.openjdk.java.net/browse/JDK-8191467

I've added Chris and Dan as reviewers and changed the state to "Proposed".
Not sure, how it should switch to the "Pended" state.


Thanks,
Serguei


> Thank you for catching this problem, David!
>
> Thanks,
> Serguei
>
>
>> has no CSR.
>>
>> David
>>
>>> Thanks,
>>> Serguei
>>>
>>>
>>> On 11/16/17 17:53, David Holmes wrote:
>>>> The CSR needs to be created again from the real bug report.
>>>> Everyone will need to re-review and re-add any necessary comments.
>>>>
>>>> David
>>>>
>>>> On 17/11/2017 11:51 AM, David Holmes wrote:
>>>>> On 17/11/2017 10:25 AM, [hidden email] wrote:
>>>>>> Dan and Chris
>>>>>>
>>>>>> Could one of you, please, review the CSR for 8187289:
>>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>>>>>>
>>>>>> Bug is:
>>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8187289
>>>>>
>>>>> The links above should not be to bugs-stage!
>>>>>
>>>>> David
>>>>>
>>>>>> Approved webrev:
>>>>>> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/ 
>>>>>>
>>>>>>
>>>>>>
>>>>>> This CSR covers a change in behavior, not in the JVMTI spec.
>>>>>> We decided that the JVMTI NotifyFramePop is intuitive enough and
>>>>>> does not need an update.
>>>>>>
>>>>>> Thanks,
>>>>>> Serguei
>>>>>>
>>>>>>
>>>>>>
>>>
>

Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

David Holmes
On 17/11/2017 3:51 PM, [hidden email] wrote:
> The CSR is:
>    https://bugs.openjdk.java.net/browse/JDK-8191467
>
> I've added Chris and Dan as reviewers and changed the state to "Proposed".

Did you intend to fast-track it? If so it should have been "Finalized"
not "Proposed".

> Not sure, how it should switch to the "Pended" state.

That for CSR group use [1]:

Pended: The chair or other CSR member has identified an issue with the
proposal that needs to be addressed before the proposal can be approved.

David

[1] https://wiki.openjdk.java.net/display/csr/Fields+of+a+CSR+Request

>
> Thanks,
> Serguei
>
>
>> Thank you for catching this problem, David!
>>
>> Thanks,
>> Serguei
>>
>>
>>> has no CSR.
>>>
>>> David
>>>
>>>> Thanks,
>>>> Serguei
>>>>
>>>>
>>>> On 11/16/17 17:53, David Holmes wrote:
>>>>> The CSR needs to be created again from the real bug report.
>>>>> Everyone will need to re-review and re-add any necessary comments.
>>>>>
>>>>> David
>>>>>
>>>>> On 17/11/2017 11:51 AM, David Holmes wrote:
>>>>>> On 17/11/2017 10:25 AM, [hidden email] wrote:
>>>>>>> Dan and Chris
>>>>>>>
>>>>>>> Could one of you, please, review the CSR for 8187289:
>>>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>>>>>>>
>>>>>>> Bug is:
>>>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8187289
>>>>>>
>>>>>> The links above should not be to bugs-stage!
>>>>>>
>>>>>> David
>>>>>>
>>>>>>> Approved webrev:
>>>>>>> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/ 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> This CSR covers a change in behavior, not in the JVMTI spec.
>>>>>>> We decided that the JVMTI NotifyFramePop is intuitive enough and
>>>>>>> does not need an update.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Serguei
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: CSR review request for: 8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled

serguei.spitsyn@oracle.com
On 11/16/17 22:08, David Holmes wrote:
> On 17/11/2017 3:51 PM, [hidden email] wrote:
>> The CSR is:
>>    https://bugs.openjdk.java.net/browse/JDK-8191467
>>
>> I've added Chris and Dan as reviewers and changed the state to
>> "Proposed".
>
> Did you intend to fast-track it? If so it should have been "Finalized"
> not "Proposed".

It feels like this CSR is a good candidate for fast-tracking but I'm not
completely sure.


>> Not sure, how it should switch to the "Pended" state.
>
> That for CSR group use [1]:
>
> Pended: The chair or other CSR member has identified an issue with the
> proposal that needs to be addressed before the proposal can be approved.
>
> David
>
> [1] https://wiki.openjdk.java.net/display/csr/Fields+of+a+CSR+Request

Ok, thanks!


Thanks,
Serguei


>> Thanks,
>> Serguei
>>
>>
>>> Thank you for catching this problem, David!
>>>
>>> Thanks,
>>> Serguei
>>>
>>>
>>>> has no CSR.
>>>>
>>>> David
>>>>
>>>>> Thanks,
>>>>> Serguei
>>>>>
>>>>>
>>>>> On 11/16/17 17:53, David Holmes wrote:
>>>>>> The CSR needs to be created again from the real bug report.
>>>>>> Everyone will need to re-review and re-add any necessary comments.
>>>>>>
>>>>>> David
>>>>>>
>>>>>> On 17/11/2017 11:51 AM, David Holmes wrote:
>>>>>>> On 17/11/2017 10:25 AM, [hidden email] wrote:
>>>>>>>> Dan and Chris
>>>>>>>>
>>>>>>>> Could one of you, please, review the CSR for 8187289:
>>>>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8191098
>>>>>>>>
>>>>>>>> Bug is:
>>>>>>>> https://bugs-stage.openjdk.java.net/browse/JDK-8187289
>>>>>>>
>>>>>>> The links above should not be to bugs-stage!
>>>>>>>
>>>>>>> David
>>>>>>>
>>>>>>>> Approved webrev:
>>>>>>>> http://cr.openjdk.java.net/%7Esspitsyn/webrevs/2017/hotspot/8187289-jvmti-framepop.2/ 
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> This CSR covers a change in behavior, not in the JVMTI spec.
>>>>>>>> We decided that the JVMTI NotifyFramePop is intuitive enough
>>>>>>>> and does not need an update.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Serguei
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>
>>>
>>