Skip to content

Commit fbb013b

Browse files
committed
Update jvmti.xml to follow CSR
1 parent 4810e98 commit fbb013b

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

src/hotspot/share/prims/jvmti.xml

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -686,12 +686,11 @@ Agent_OnUnload_L(JavaVM *vm)</example>
686686
The library will be unloaded (unless it is statically linked into the
687687
executable) and this function will be called if some platform specific
688688
mechanism causes the unload (an unload mechanism is not specified in this document)
689-
or the library is (in effect) unloaded by the termination of the VM whether through
690-
normal termination or VM failure, including start-up failure.
691-
Uncontrolled shutdown and Agent Start-Up failure
692-
(<internallink id="onload"><code>Agent_OnLoad</code></internallink> and
693-
<internallink id="onattach"><code>Agent_OnAttach</code></internallink>) are, of course,
694-
an exception to this rule.
689+
or the library is (in effect) unloaded by the termination of the VM.
690+
VM termination includes normal termination and VM failure, including start-up failure,
691+
but not, of course, uncontrolled shutdown. An implementation may also
692+
choose to not call this function if the <code>Agent_OnAttach</code>/
693+
<code>Agent_OnAttach_L</code> function reported an error (returned a non-zero value).
695694
Note the distinction between this function and the
696695
<eventlink id="VMDeath">VM Death event</eventlink>: for the VM Death event
697696
to be sent, the VM must have run at least to the point of initialization and a valid

0 commit comments

Comments
 (0)