title: incomplete backtrace in logcat
body: <p>When my Android app crashes (or hits an assert), I never get more than four lines of backtrace. Searching for similar problems, I've only found one or two places where this is mentioned and the stock responses are: "make sure it's a debug build" and "you probably have stack corruption". I have seen many crashes occur in many places with accurate-looking frames and no evidence of corruption.</p>
  
  <p>Here's a typical excerpt taken from `adb logcat' following an assert failure in a debug build:</p>
  
  <pre><code>I/DEBUG   (  187):     d28 3f824fc6ced25306  d29 3fabdfebb8fe14dc
  I/DEBUG   (  187):     d30 fff0000000000000  d31 fffffffeffffffd2
  I/DEBUG   (  187):     scr 88000010
  I/DEBUG   (  187): 
  I/DEBUG   (  187): backtrace:
  I/DEBUG   (  187):     #00  pc 00018516  /system/lib/libc.so
  I/DEBUG   (  187):     #01  pc 0000dc44  /system/lib/libc.so (abort+4)
  I/DEBUG   (  187):     #02  pc 0000168d  /system/lib/liblog.so (__android_log_assert+88)
  I/DEBUG   (  187):     #03  pc 00170bcc  /data/data/com.jsam.crag/lib/libmain.so (sim::TouchObserverController::HandleEvent(SDL_Event const&amp;)+340)
  I/DEBUG   (  187): 
  I/DEBUG   (  187): stack:
  I/DEBUG   (  187):          6f4be770  6f4be76c  [stack:17025]
  I/DEBUG   (  187):          6f4be774  00000000  
  I/DEBUG   (  187):          6f4be778  00000000  
  </code></pre>
  
  <p>As you can see, most of the available backtrace isn't even in my own code. I'm developing on a developer edition HTC One with out-of-box OS, using release 8e of the NDK and building against android-10, although android-15 is no different. I'm using toolchain v4.7, the gnustl_static STL and my C++ flags are:</p>
  
  <pre><code>-std=c++11 -g -pthread -DPROFILE -D__STRICT_ANSI__ -DdSINGLE -Wall -Wextra -Wfatal-errors -fno-rtti -fno-exceptions
  </code></pre>
  
  <p>How would I go about getting longer (preferably complete) backtraces?</p>