Databases
StackOverflow2013
Postsdbo
POstack traces stop before getting to my code (on Android using NDK)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POstack traces stop before getting to my code (on Android using NDK)
    primarykey
    data
    text
    <p>I'm developing on Android 2.3.x using NDK r5b. Occasionally my code crashes and I'd like to know where. I already know how to get the corresponding line in my application when I have a have a pointer (i.e. from Android's stack traces.)</p> <p>However, oftentimes I see useless stack traces like this (full stack trace):</p> <pre><code> #00 pc 0006561a /system/lib/egl/libGLESv2_adreno200.so #01 pc 0006b900 /system/lib/egl/libGLESv2_adreno200.so #02 pc 0005aac8 /system/lib/egl/libGLESv2_adreno200.so #03 pc 0001687a /system/lib/egl/libGLESv1_CM_adreno200.so #04 pc 000096ce /system/lib/egl/libGLESv1_CM_adreno200.so </code></pre> <p>or this:</p> <pre><code>(gdb) bt #0 0xafd0c51c in epoll_wait () from /Volumes/SecureCode/webos/rta/android/obj/local/armeabi/libc.so #1 0xa81216a6 in ?? () </code></pre> <p>that don't even mention my code at all.</p> <p>Is there any way at all to get better stack traces than this? Why are some library functions "opaque" in that they don't allow the backtrace to "see through" to the calling function, causing a stop in the stack trace?</p> <p>As far as I can tell, the only way to debug a problem like this is to use logging at each point in the program and/or step through each line with gdb.</p> <p>Are there ROMs available with debug versions of these Android libraries instead of runtime ones, and would that help? (I use one phone solely for development, so I'm not concerned about keeping full functionality.) (<em><strong>Actually</strong></em>, I noticed that the path to <code>libc.so</code> in the above <code>gdb</code> stack trace is within my application directory. Could I possibly just package it with a different (debug) <code>libc.so</code>, and would that help?)</p> <p>One last thing that might help: in the above stack trace from logcat (the first one,) my library is mentioned in the raw stack dump:</p> <pre><code>stack: ... ... 4471cb88 00000028 4471cb8c afd4649c 4471cb90 80b4eb71 /data/data/com.audia.dev.rta/lib/librta.so 4471cb94 00299180 ... ... </code></pre> <p>but that is not a function pointer. What could that be, and would it be of any help after the app has crashed? I'm guessing probably not if it's a heap pointer or something like that.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStmandry
    1. UStmandry
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POstack traces stop before getting to my code (on Android using NDK)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POstack traces stop before getting to my code (on Android using NDK)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POstack traces stop before getting to my code (on Android using NDK)
      1. UStmandry
      1. VTBountyStart
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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