Use findRangeByAddress instead of findModuleByAddress when checking i…

…f the stack pointer is valid
HHucKer · Jul 29, 2019 · a3adab3 · a3adab3
1 parent 5944397
commit a3adab3
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # jnitrace Change Log
 
+## 1.3.2
+- Bug fix - Use Process.findRangeByAddress instead of Process.findModuleByAddress for checking the validity of the stack pointer
+
+## 1.3.1
+- Travis integration
+
 ## 1.3.0
 - Added a command argument to get the version of jnitrace
 - jnitrace now intercepts calls to GetJavaVM, returning a shadowJavaVM

diff --git a/jnitrace/src/transport/trace_transport.js b/jnitrace/src/transport/trace_transport.js
@@ -195,7 +195,7 @@ TraceTransport.prototype.trace = function(method, args, ret, context, add) {
   // verify that a backtrace is possible.
   // sometimes the NativeCallback provides erroneous CpuContexts
   if (Process.findModuleByAddress(context.pc) &&
-        Process.findModuleByAddress(context.sp)) {
+        Process.findRangeByAddress(context.sp)) {
     var bt = Thread.backtrace(context, Backtracer.FUZZY);
 
     for (var i = 0; i < bt.length; i++) {

diff --git a/setup.py b/setup.py
@@ -8,7 +8,7 @@
 
 setup(
     name='jnitrace',
-    version='1.3.1',
+    version='1.3.2',
     description='A tool for tracing use of the JNI in Android apps',
     long_description=long_description,
     long_description_content_type='text/markdown',