search

davidbrs / google-breakpad

Automatically exported from code.google.com/p/google-breakpad
0 stars 0 forks source link

android dump_syms return error : file contains no debugging information (no ".stab" or ".debug_info" sections) #633

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.I follow the README.ANDROID step by step,when i generate symbols file use 
dump_syms xxx.so > xxx.so.sym, i get a error:

xxx.so: file contains no debugging information (no ".stab" or ".debug_info" 
sections)
--------------------------------------------------------------------------------
-----
xxx.so is in the obj/local/armeabi
use file xxx.so show "xxx.so ELF 32-bit LSB shared object, ARM, version 1 
(SYSV), dynamically linked (uses shared libs), not stripped"

And i tried to modify Application.mk:
a.change APP_STL but noting work
#APP_STL := gnustl_shared
#APP_STL := gnustl_static
#APP_STL := stlport_static

b.change APP_OPTIM but noting work
APP_OPTIM := release
APP_OPTIM := debug

What should i do for this?

What version of the product are you using? On what operating system?
i use android-ndk-r10d

Original issue reported on code.google.com by nwpudon...@gmail.com on 6 Feb 2015 at 7:46

GoogleCodeExporter commented 9 years ago 
"file contains no debugging information" is not a fatal error. It's just 
dump_syms telling you xxx.so, erm, does not have any debugging information. The 
generated .sym file will not have detailed information.

If xxx.so has a .gnu_debuglink for xxx.so.debug, then run: dump_syms xxx.so 
/path/to/directory/that/contains_xxx.so.debug/

Original comment by thestig@chromium.org on 6 Feb 2015 at 8:35