No subject


Mon Feb 7 10:29:41 EST 2005


> I think this is strange because how else would the GCC_3.0 symbol
> (or whatever it is) get in glibc unless it was built with gcc3?

Can you give the command given this symbol or the meaning of symbol
$ objdump -t /lib/libc.so.6 | grep GCC
00000000 g     O *ABS*  00000000              GCC_3.0

$ objdump -T /lib/libc.so.6 | grep GCC
001124c0 g    DF .text  0000008d  GCC_3.0     _Unwind_Find_FDE
00000000 g    DO *ABS*  00000000  GCC_3.0     GCC_3.0
00111b88 g    DF .text  00000090  GCC_3.0     __register_frame_info_bases
00111f14 g    DF .text  000000f2  GCC_3.0     __deregister_frame_info_bases
00111d58 g    DF .text  00000090  GCC_3.0     __register_frame_info_table_bases

> So I used strings on libc.so.6 

$ objdump -T /lib/libc.so.6 | grep string
0007fcec  w   DF .text  0000004c  GLIBC_2.0   argz_stringify
00105afc g    DF .text  0000002f  GLIBC_2.0   xdr_wrapstring
00105894 g    DF .text  00000268  GLIBC_2.0   xdr_string
0007fcec g    DF .text  0000004c  GLIBC_2.0   __argz_stringify

> and it tells me that it was compiled with gcc2.96. So how
> would that symbol have gotten there anyway?



More information about the OCLUG mailing list