StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>Is there any way at all to get better stack traces than this?</p> </blockquote> <p>As far as I know, you must build and write the Android image by yourself. It enables you to have the whole complete symbols of the Android (executable files and shared libraries) except proprietary shared libraries.</p> <ul> <li><a href="http://wiki.cyanogenmod.com/wiki/Building_from_source" rel="noreferrer">Building from source - Compile CyanogenMod from Source</a></li> </ul> <p>Also it provides to use the symbols using gdb.</p> <pre><code>$ adb shell setprop debug.db.uid 32767 $ adb forward tcp:5039 tcp:5039 /* program terminated and debuggerd caught exception like the following. Use the PID number for gdbclient 3rd parameter. I/DEBUG ( 2154): ******************************************************** I/DEBUG ( 2154): * Process 2508 has been suspended while crashing. To I/DEBUG ( 2154): * attach gdbserver for a gdb connection on port 5039: I/DEBUG ( 2154): * I/DEBUG ( 2154): * adb shell gdbserver :5039 --attach 2508 & I/DEBUG ( 2154): * I/DEBUG ( 2154): * Press HOME key to let the process continue crashing. I/DEBUG ( 2154): ********************************************************) */ $ gdbclient "" "" 2508 </code></pre> <p><strong>EDITED:</strong></p> <p>You can still use ndk-gdb instead of gdbclient command. Please specify the symbol files for shared libraries.</p> <pre><code>(gdb) set solib-search-path (ANDROID_SOURCE_PATH)/out/target/product/(PRODUCT_NAME)/symbols/system/lib </code></pre> <p><strong>EDITED 2:</strong></p> <p>If you don't need the symbols of the Android system shared libraries, just adb pull shared libraries and set sollib-search-path to it.</p> <pre><code>$ adb pull /system/lib lib $ ndk-gdb ... (gdb) set solib-search-path lib </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload