stan/jdk-24
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

8294924: JvmtiExport::post_exception_throw() doesn't deal well with concurrent stack processing

Browse Source 
Reviewed-by: pchilanomate, sspitsyn, dholmes
This commit is contained in:
Erik Österlund 2022-11-30 14:15:18 +00:00
parent be99e84c98
commit be4245e814
1 changed files with 6 additions and 0 deletions

6
src/hotspot/share/prims/jvmtiExport.cpp

@ -60,6 +60,7 @@
#include "runtime/javaCalls.hpp"
#include "runtime/javaThread.hpp"
#include "runtime/jniHandles.inline.hpp"
#include "runtime/keepStackGCProcessed.hpp"
#include "runtime/objectMonitor.hpp"
#include "runtime/objectMonitor.inline.hpp"
#include "runtime/os.hpp"
@ -1964,6 +1965,11 @@ void JvmtiExport::post_exception_throw(JavaThread *thread, Method* method, addre
HandleMark hm(thread);
methodHandle mh(thread, method);
Handle exception_handle(thread, exception);
// The KeepStackGCProcessedMark below keeps the target thread and its stack fully
// GC processed across this scope. This is needed because there is a stack walk
// below with safepoint polls inside of it. After such safepoints, we have to
// ensure the stack is sufficiently processed.
KeepStackGCProcessedMark ksgcpm(thread);
JvmtiThreadState *state = thread->jvmti_thread_state();
if (state == NULL) {