I'm building an NDK shared library with a static library (.a) as one of the inputs. The static library has debug info in GDB format. Does the debug info end up in the final .SO? How can I check?
Asked
Active
Viewed 4,624 times
1 Answers
6
Yes it does. The final step of NDK build is copying the .so file from obj directory to lib, stripping the symbols on the way. You can see how much smaller the file gets in lib/armeabi.
Alex Cohn
- 56,089
- 9
- 113
- 307
-
1Is keeping symbols somewhere aside an option? – Seva Alekseyev Oct 10 '12 at 20:46
-
1You can use the `obj/` copy for debugging. – Alex Cohn Oct 10 '12 at 20:57
-
Not sure how exactly (I'm after interpreting runtime crashes on user devices), but thanks for the hint. – Seva Alekseyev Oct 10 '12 at 20:59
-
@AlexCohn how do you do this? if I copy it from obj to libs, then run, it just gets a new small version again put in the lib folder. And will this give me a readable call stack during a seg fault? – weston Nov 16 '12 at 21:29
-
@weston: please read http://stackoverflow.com/questions/8218507/ndk-stack-not-working – Alex Cohn Nov 16 '12 at 23:07