Skip to content

Commit

Permalink
8307531: [aarch64] JDK8 single-step debugging is extremely slow
Browse files Browse the repository at this point in the history
Reviewed-by: aph
  • Loading branch information
Sergey Nazarkin authored and Yuri Nesterenko committed May 12, 2023
1 parent 4328fec commit 3e69b49
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 7 deletions.
7 changes: 0 additions & 7 deletions hotspot/src/share/vm/prims/jvmtiExport.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -1239,14 +1239,7 @@ void JvmtiExport::post_method_exit(JavaThread *thread, Method* method, frame cur
}
}

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


Expand Down
1 change: 1 addition & 0 deletions hotspot/src/share/vm/prims/jvmtiThreadState.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,7 @@ JvmtiThreadState::JvmtiThreadState(JavaThread* thread)
_vm_object_alloc_event_collector = NULL;
_the_class_for_redefinition_verification = NULL;
_scratch_class_for_redefinition_verification = NULL;
_cur_stack_depth = UNKNOWN_STACK_DEPTH;

// JVMTI ForceEarlyReturn support
_pending_step_for_earlyret = false;
Expand Down

1 comment on commit 3e69b49

@openjdk-notifier
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.