aboutsummaryrefslogtreecommitdiff
path: root/en/devices/tech/debug/native-crash.html
diff options
context:
space:
mode:
authorAndroid Partner Docs <noreply@android.com>2017-06-23 13:18:39 -0700
committerClay Murphy <claym@google.com>2017-06-26 13:40:01 -0700
commitcb2b2fcd6e35be6139157b1f401b2cc81b61679f (patch)
tree993d64201a783b91d3b9ad990ebe30afca79c960 /en/devices/tech/debug/native-crash.html
parent14605d77b5e0aabc741b2b69d53e9e772f010b23 (diff)
downloadsource.android.com-cb2b2fcd6e35be6139157b1f401b2cc81b61679f.tar.gz
Docs: Changes to source.android.com
- 159984637 Remove stale information from known issues page by daroberts <daroberts@google.com> - 159713438 Fixed spelling error in terminal command and removed extr... by cqn <cqn@google.com> - 159634352 Fix name of SEEC driver by claym <claym@google.com> - 159628057 Remove unneeded closing tag by cqn <cqn@google.com> - 159627213 Remove unneeded closing tags by cqn <cqn@google.com> - 159627180 Fix minor tag nesting issue by cqn <cqn@google.com> - 159627159 Fixed HTML tag nesting by cqn <cqn@google.com> - 159626603 Add missing closing tags by cqn <cqn@google.com> - 159626543 Remove unneeded tag by cqn <cqn@google.com> - 159626515 Fix tag nesting by cqn <cqn@google.com> - 159626453 Changed tag nesting issues by cqn <cqn@google.com> - 159626442 Add missing tag by cqn <cqn@google.com> - 159625955 Added missing paragraph tags by cqn <cqn@google.com> - 159625722 Fixed header closing tag by cqn <cqn@google.com> - 159625168 Delete unneeded code tag by cqn <cqn@google.com> - 159624516 Add note explaining dollar sign in sample commands by claym <claym@google.com> - 159615772 Delete unneeded </code> tags by cqn <cqn@google.com> - 159615658 Added missing closing tag by cqn <cqn@google.com> - 159612512 Removed a couple unneeded <p> tags by cqn <cqn@google.com> - 159612476 Add missing <p> tag by cqn <cqn@google.com> PiperOrigin-RevId: 159984637 Change-Id: Ib9f6f4905c548fc113dc0724e3e776ad8685a628
Diffstat (limited to 'en/devices/tech/debug/native-crash.html')
-rw-r--r--en/devices/tech/debug/native-crash.html11
1 files changed, 6 insertions, 5 deletions
diff --git a/en/devices/tech/debug/native-crash.html b/en/devices/tech/debug/native-crash.html
index c1658cc5..00f72cd0 100644
--- a/en/devices/tech/debug/native-crash.html
+++ b/en/devices/tech/debug/native-crash.html
@@ -46,7 +46,7 @@ using one of the Android-specific fatal logging types), but they all involve
calling <code>abort</code>. A call to <code>abort</code> basically signals the
calling thread with SIGABRT, so a frame showing "abort" in <code>libc.so</code>
plus SIGABRT are the things to look for in the <code>debuggerd</code> output to
-recognize this case.
+recognize this case.</p>
<p>
As mentioned above, there may be an explicit "abort message" line. But you
@@ -83,7 +83,7 @@ backtrace:
More recent versions call <code><a
href="http://man7.org/linux/man-pages/man2/tgkill.2.html">tgkill(2)</a></code>
directly from <code>abort</code>, so there are fewer stack frames for you to
-skip over before you get to the interesting frames:
+skip over before you get to the interesting frames:</p>
<pre class="devsite-click-to-copy">
pid: 25301, tid: 25301, name: crasher >>> crasher <<<
@@ -155,6 +155,7 @@ href="http://man7.org/linux/man-pages/man3/fopen.3.html">fopen(3)</a></code> or
<code><a
href="http://man7.org/linux/man-pages/man3/opendir.3.html">opendir(3)</a></code>
call actually succeeded first.
+</p>
<p>
Here's an example of <code>readdir</code>:
@@ -192,7 +193,7 @@ offset <code>sizeof(int) + sizeof(size_t) + sizeof(dirent*)</code> into
<code>struct DIR</code>, which on a 32-bit device is 4 + 4 + 4 = 12 = 0xc, so
you found the bug: <code>readdir</code> was passed a null pointer by the caller.
At this point you can paste the stack into the stack tool to find out
-<em>where</em> in logcat this happened.
+<em>where</em> in logcat this happened.</p>
<pre class="prettyprint">
struct DIR {
@@ -396,7 +397,7 @@ ip 00000006 sp ff96ad18 lr f700ced5 pc f700dc98 cpsr 400b0010
<p>The register dump shows the content of the CPU registers at the time the
signal was received. (This section varies wildly between ABIs.) How useful
-these are will depend on the exact crash.<p>
+these are will depend on the exact crash.</p>
<pre class="devsite-click-to-copy">
backtrace:
@@ -464,7 +465,7 @@ that can be recognized by looking at the maps include:</p>
will show the BuildId (if present) in Android M and later, so you can see
exactly which version of your code crashed. (Platform binaries include a
BuildId by default since Android M. NDK r12 and later automatically pass
-<code>-Wl,--build-id</code> to the linker too.)<p>
+<code>-Wl,--build-id</code> to the linker too.)</p>
<pre class="devsite-click-to-copy">
ab163000-ab163fff r-- 3000 1000 /system/xbin/crasher