From 9f1020305292a21fd14a402b189c765a125226ab Mon Sep 17 00:00:00 2001 From: Sebastien Hertz Date: Fri, 23 May 2014 08:59:42 +0200 Subject: Fix exception reporting from interpreter To comply with JDWP exception report rules, we must report an exception at the location of the throw (or the first instruction encountered after a native call). To do this, we use the CatchLocationFinder visitor to look for a catch handler until we reach a native frame or the top frame. Because interpreter handles pending exception on a method-by-method basis, we need a flag to remember we already reported the exception and avoid reporting it multiple times when unwinding methods. The drawback is we need to maintain the state of this flag. We clear it when the exception is cleared. In the case we temporarily clear the exception (when finding a catch handler for instance), we restore the flag to its previous value at the same time we restore the pending exception. Bump oat version to force recompilation because we modify Thread offsets. Bug: 14402770 Change-Id: Ic059c58f80b2023b118038301f8f0a24f1e18241 --- runtime/quick_exception_handler.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'runtime/quick_exception_handler.h') diff --git a/runtime/quick_exception_handler.h b/runtime/quick_exception_handler.h index a4229b3..1d600ed 100644 --- a/runtime/quick_exception_handler.h +++ b/runtime/quick_exception_handler.h @@ -42,7 +42,8 @@ class QuickExceptionHandler { LOG(FATAL) << "UNREACHABLE"; // Expected to take long jump. } - void FindCatch(const ThrowLocation& throw_location, mirror::Throwable* exception) + void FindCatch(const ThrowLocation& throw_location, mirror::Throwable* exception, + bool is_exception_reported) SHARED_LOCKS_REQUIRED(Locks::mutator_lock_); void DeoptimizeStack() SHARED_LOCKS_REQUIRED(Locks::mutator_lock_); void UpdateInstrumentationStack() SHARED_LOCKS_REQUIRED(Locks::mutator_lock_); -- cgit v1.1