Skip to content
Permalink
Browse files

8221306: JVMTI spec for FramePop(), MethodExit(), and MethodEnter() c…

…ould use some cleanup

JVMTI spec cleanup for functions FramePop(), MethodExit(), and MethodEnter()

Reviewed-by: cjplummer, amenkov
  • Loading branch information
Serguei Spitsyn
Serguei Spitsyn committed Jun 2, 2020
1 parent 7e862f9 commit ddbc7ed0a1008663ab331dab1e6cd64411f22fb4
Showing with 3 additions and 8 deletions.
  1. +3 −8 src/hotspot/share/prims/jvmti.xml
@@ -12283,7 +12283,7 @@ myInit() {
function are not reported.
<p/>
The location reported by <functionlink id="GetFrameLocation"></functionlink>
identifies the executable location in the returning method,
for the depth 0 identifies the executable location in the returning method,
immediately prior to the return.
</description>
<origin>jvmdi</origin>
@@ -12334,8 +12334,7 @@ myInit() {
programming language methods (including native methods).
<p/>
The location reported by <functionlink id="GetFrameLocation"></functionlink>
identifies the initial executable location in
the method.
for the depth 0 identifies the initial executable location in the method.
<p/>
Enabling method
entry or exit events will significantly degrade performance on many platforms and is thus
@@ -12387,12 +12386,8 @@ myInit() {
or by throwing an exception to its caller
(see <paramlink id="was_popped_by_exception"></paramlink>).
<p/>
The <code>method</code> field uniquely identifies the
method being entered or exited. The <code>frame</code> field provides
access to the stack frame for the method.
<p/>
The location reported by <functionlink id="GetFrameLocation"></functionlink>
identifies the executable location in the returning method
for the depth 0 identifies the executable location in the returning method
immediately prior to the return.
<p/>
Enabling method

0 comments on commit ddbc7ed

Please sign in to comment.
You can’t perform that action at this time.