Hi, 郭涛 wrote, > Hello > > I have a static linked binary, I want run it on a mipsel_24kc platform > with uclibc-ng-1.0.22. > But when I run it, it show Segmentation fault. I only have the binary, > no source code > This binary can run with uclibc0.9.33, have you any suggestion ?
This just look strange to me. You are saying the binary is statically linked. What do you mean exactly? Because when the binary is statically linked _all_ code is included in the application including C library code. In the following debug output we are seeing that the shared library loader ld-uClibc.so.0 is used. > exec output > _dl_get_ready_to_run:461: Cool, ldso survived making function calls > _dl_malloc:237: mmapping more memory > _dl_get_ready_to_run:671: calling mprotect on the application program > _dl_get_ready_to_run:1065: Loading: (0x772f1000) /lib/libdl.so.0 > _dl_get_ready_to_run:1065: Loading: (0x772ce000) /lib/libgcc_s.so.1 > _dl_load_elf_shared_library:825: Found TLS header for /lib/libc.so.0 > _dl_load_elf_shared_library:852: Relocated TLS initial image from > 0x93ee4 to 0x772b5ee4 (size = 0x4) > _dl_get_ready_to_run:1065: Loading: (0x77222000) /lib/libc.so.0 > _dl_get_ready_to_run:1065: Loading: (0x77222000) /lib/libc.so.0 > _dl_get_ready_to_run:1065: Loading: (0x7730c000) /lib/ld-uClibc.so.0 > _dl_get_ready_to_run:1206: Calling init_tls()! > _dl_malloc:237: mmapping more memory > _dl_get_ready_to_run:1306: Beginning relocation fixups > _dl_get_ready_to_run:1336: Calling _dl_allocate_tls_init()! > Segmentation fault Can you clarify the situation? Can you show "file yourapp" and maybe "readelf -a yourapp"? best regards Waldemar _______________________________________________ devel mailing list devel@uclibc-ng.org https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel
