OpenJDK / jdk / jdk
changeset 59571:141d1bde85ec
8221306: JVMTI spec for FramePop(), MethodExit(), and MethodEnter() could use some cleanup
Summary: JVMTI spec cleanup for functions FramePop(), MethodExit(), and MethodEnter()
Reviewed-by: cjplummer, amenkov
| author | sspitsyn |
|---|---|
| date | Tue, 02 Jun 2020 19:34:19 +0000 |
| parents | 0588bb1994e3 |
| children | d854e682f6a9 |
| files | src/hotspot/share/prims/jvmti.xml |
| diffstat | 1 files changed, 3 insertions(+), 8 deletions(-) [+] |
line wrap: on
line diff
--- a/src/hotspot/share/prims/jvmti.xml Tue Jun 02 12:16:58 2020 -0700 +++ b/src/hotspot/share/prims/jvmti.xml Tue Jun 02 19:34:19 2020 +0000 @@ -12283,7 +12283,7 @@ 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 @@ 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 @@ 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