[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Status update hppa - glibc 2.2.92 (Problems with __divdi3)



> Note that you will want the current version of divdi3.c which only
> presents the symbols for runtime resolution and not exported for linking.
> You can check this in a build by doing...
> 
> objdump --dynamic-sym ./libc.so.6 | grep __divdi3
> 

As far as I can tell our libc on hppa doesn't export any libgcc symbols.
The above line returns nothing. I've also exported all the symbols in libgcc
and tried to match them to dynamic-syms in libc and haven't found any.

hppa has always been compiled with gcc-3.0.

nm -a /usr/lib/gcc-lib/hppa-linux/3.0.4/libgcc.a | grep __ | grep -v "^__" > __outlist.txt
cat __outlist.txt | sed 's/^.* . //g' > symlist.txt
for i in `cat symlist.txt`; do objdump --dynamic-syms /lib/libc.so.6 | grep $i; done;

0011396c g    DF .text  00000018  GLIBC_2.2   __deregister_frame_info
0011382c g    DF .text  00000140  GCC_3.0     __deregister_frame_info_bases
0011396c g    DF .text  00000018  GLIBC_2.2   __deregister_frame_info
0011382c g    DF .text  00000140  GCC_3.0     __deregister_frame_info_bases
0011382c g    DF .text  00000140  GCC_3.0     __deregister_frame_info_bases
001135d8 g    DF .text  000000bc  GCC_3.0     __register_frame_info_bases
0011370c g    DF .text  000000c0  GCC_3.0     __register_frame_info_table_bases
00113694 g    DF .text  00000020  GLIBC_2.2   __register_frame_info
001135d8 g    DF .text  000000bc  GCC_3.0     __register_frame_info_bases
0011370c g    DF .text  000000c0  GCC_3.0     __register_frame_info_table_bases
00113694 g    DF .text  00000020  GLIBC_2.2   __register_frame_info
001135d8 g    DF .text  000000bc  GCC_3.0     __register_frame_info_bases
0011370c g    DF .text  000000c0  GCC_3.0     __register_frame_info_table_bases
0011370c g    DF .text  000000c0  GCC_3.0     __register_frame_info_table_bases
000220f0  w   DF .text  00000010  GLIBC_2.2   __errno_location

These look harmless, and properly versioned?

c.



Reply to: