To confirm this I wrote a simple test program and compiled it using
`arm-eabi-gcc ${FLAGS} -c`. Analyzing the symbol table with `nm` again
revealed this problem:
arm-eabi-nm *.o
00000000 r .LC0
00000008 r .LC1
U _GLOBAL_OFFSET_TABLE_
U __aeabi_unwind_cpp_pr0
U __aeabi_unwind_cpp_pr1
00000000 T func1
00000000 T func2
00000000 T main
U printf
Strangely though, the program links successfully (`arm-eabi-gcc $
{FLAGS} *.o -o hello`) , and the final executable can run on the
emulator. It also shows a legitimate symbol table. Could someone
please enlighten me what's causing this bhavior?
--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-ndk...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-ndk?hl=en.
On Jan 7, 3:02 pm, David Turner <di...@android.com> wrote:
> This is normal for object files. The symbols have non zero values for
> executables and shared libraries which are assigned by the final linker.
>
> > android-ndk...@googlegroups.com<android-ndk%2Bunsu...@googlegroups.com>
Is this behavior specific to the ndk? Both the default x86 toolchain
on Ubuntu and codesourcery arm toolchain produce object files with
valid symbol tables.
To unsubscribe from this group, send email to android-ndk...@googlegroups.com.
On Jan 7, 5:33 pm, David Turner <di...@android.com> wrote:
> > <android-ndk%2Bunsu...@googlegroups.com<android-ndk%252Buns...@googlegroups.com>