Hi While trying to debug native C libraries, upon receiving a SIGSEGV, the core dump thrown does not map address values to symbols as seen in DDMS. As mentioned above this is happening due to stripping of binaries. How can we prevent such stripping in Android or obtain detailed stack trace despite stripping ? Are there any changes we need to make to the Makefiles ?
Thanks in advance On Feb 13, 1:47 am, fadden <fad...@android.com> wrote: > On Feb 12, 1:59 am, "click...@gmail.com" <click...@gmail.com> wrote: > > > I am looking for little more informations rather than Hex values. > > Like the backtrace feature where the stack hex values is mapped to the > > function names and function names are visible. > > The device can't show these, because the symbols are stripped out of > the libraries before they are installed on the device. They do exist > in the build tree; since you're doing your own builds, you can find > them in the appropriate "symbols" directory under "out/". > > Given that, you can use "arm-eabi-addr2line" to convert the symbols, > or use gdb/gdbserver to do debugging directly on the device. Make > sure you're using the "out" directory that corresponds to the binaries > installed on the device. > > In any event, discussions about debugging native libraries might be > more appropriate for android-porting or android-platform at this time. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
