Skip to content

Commit 3e69b49

Browse files
Sergey NazarkinYuri Nesterenko
authored andcommitted
8307531: [aarch64] JDK8 single-step debugging is extremely slow
Reviewed-by: aph
1 parent 4328fec commit 3e69b49

File tree

2 files changed

+1
-7
lines changed

2 files changed

+1
-7
lines changed

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

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1239,14 +1239,7 @@ void JvmtiExport::post_method_exit(JavaThread *thread, Method* method, frame cur
12391239
}
12401240
}
12411241

1242-
#ifdef AARCH64
1243-
// FIXME: this is just a kludge to get JVMTI going. Compiled
1244-
// MethodHandle code doesn't call the JVMTI notify routines, so the
1245-
// stack depth we see here is wrong.
1246-
state->invalidate_cur_stack_depth();
1247-
#else
12481242
state->decr_cur_stack_depth();
1249-
#endif
12501243
}
12511244

12521245

hotspot/src/share/vm/prims/jvmtiThreadState.cpp

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,7 @@ JvmtiThreadState::JvmtiThreadState(JavaThread* thread)
6363
_vm_object_alloc_event_collector = NULL;
6464
_the_class_for_redefinition_verification = NULL;
6565
_scratch_class_for_redefinition_verification = NULL;
66+
_cur_stack_depth = UNKNOWN_STACK_DEPTH;
6667

6768
// JVMTI ForceEarlyReturn support
6869
_pending_step_for_earlyret = false;

0 commit comments

Comments
 (0)