summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author Ryo Hashimoto <hashimoto@google.com> 2015-09-24 06:22:00 +0000
committer Android (Google) Code Review <android-gerrit@google.com> 2015-09-24 06:22:00 +0000
commita316536528e94743cbda09e82aba325de7a869cf (patch)
tree787f1be0fa479dc060f555fa52b071e0d34f5433
parent22a78887de3f7c49c4c5834cf908d32ff2f0df52 (diff)
parentb4982b20cde31e4c507c762c448e00ac820e6264 (diff)
Merge "Use the proper variant of String#substring to report broken strict mode stacks"
-rw-r--r--core/java/android/os/StrictMode.java2
1 files changed, 1 insertions, 1 deletions
diff --git a/core/java/android/os/StrictMode.java b/core/java/android/os/StrictMode.java
index 87ce12cbe37c..8b2c74f07598 100644
--- a/core/java/android/os/StrictMode.java
+++ b/core/java/android/os/StrictMode.java
@@ -1923,7 +1923,7 @@ public final class StrictMode {
if (LOG_V) Log.d(TAG, "strict mode violation stacks read from binder call. i=" + i);
ViolationInfo info = new ViolationInfo(p, !currentlyGathering);
if (info.crashInfo.stackTrace != null && info.crashInfo.stackTrace.length() > 30000) {
- String front = info.crashInfo.stackTrace.substring(256);
+ String front = info.crashInfo.stackTrace.substring(0, 256);
// 30000 characters is way too large for this to be any sane kind of
// strict mode collection of stacks. We've had a problem where we leave
// strict mode violations associated with the thread, and it keeps tacking