Support for resolving unknown direct/static methods.
If we can't resolve a method we don't know whether it is direct or
static from the dex information (other than the invocation instruction).
Add support for a third type of resolution stub that can discover the
type of the method based on the calling method and PC of the invocation
instruction. Its still unimplemented to look up the instruction and
figure out if the type is static or not.
Change-Id: I8b76e6ba2c946376e7fe287dbcca17bcaab0e133
diff --git a/src/exception_test.cc b/src/exception_test.cc
index fd012cd..49a5266 100644
--- a/src/exception_test.cc
+++ b/src/exception_test.cc
@@ -99,7 +99,7 @@
ASSERT_EQ(sizeof(uintptr_t), sizeof(uint32_t));
// Create two fake stack frames with mapping data created in SetUp. We map offset 3 in the code
- // two dex pc 3, however, we set the return pc to 5 as the stack walker always subtracts two
+ // to dex pc 3, however, we set the return pc to 5 as the stack walker always subtracts two
// from a return pc.
// Create/push fake 16byte stack frame for method g