ARM GCC-4.2.1 dynamically linked busybox-1.15.0 failed
Teh Kok How
khteh at smartbridges.com
Tue Sep 15 04:06:31 UTC 2009
Hi;
All the necessary binaries are in the NFS rootfs /lib:
-rwxrwxrwx 1 khteh root 433947 Sep 15 05:00 ld-2.3.6.so
-rwxrwxrwx 1 khteh root 10424 Aug 25 05:20 libSegFault.so
-rwxrwxrwx 1 khteh root 10075081 Sep 15 04:58 libc-2.3.6.so
-rwxrwxrwx 1 khteh root 220 Aug 22 08:41 libc.so
lrwxrwxrwx 1 khteh root 22 Aug 25 04:24 libcgic.so ->
/sbapps/lib/libcgic.so
-rwxrwxrwx 1 khteh root 21972 Aug 25 05:20 libcrypt-2.3.6.so
lrwxrwxrwx 1 khteh root 13 Aug 22 10:37 libcrypt.so -> libcrypt.so.1
-rwxrwxrwx 1 khteh root 61883 Sep 15 05:05 libdl-2.3.6.so
lrwxrwxrwx 1 khteh root 10 Aug 22 10:37 libdl.so -> libdl.so.2
lrwxrwxrwx 1 khteh root 11 Aug 20 22:38 libiw.so -> libiw.so.28
-rwxrwxrwx 1 khteh root 1313531 Sep 15 04:57 libm-2.3.6.so
lrwxrwxrwx 1 khteh root 9 Aug 22 10:38 libm.so -> libm.so.6
lrwxrwxrwx 1 khteh root 11 Aug 20 22:36 libnsl.so -> libnsl.so.1
lrwxrwxrwx 1 khteh root 15 Aug 20 22:36 libnss_dns.so ->
libnss_dns.so.2
lrwxrwxrwx 1 khteh root 17 Aug 20 22:36 libnss_files.so ->
libnss_files.so.2
-rwxrwxrwx 1 khteh root 67240 Aug 25 05:20 libpthread-0.10.so
-rwxrwxrwx 1 khteh root 204 Aug 22 08:42 libpthread.so
-rwxrwxrwx 1 khteh root 59476 Aug 25 05:20 libresolv-2.3.6.so
lrwxrwxrwx 1 khteh root 14 Aug 22 10:38 libresolv.so -> libresolv.so.2
-rwxrwxrwx 1 khteh root 31220 Aug 25 05:20 librt-2.3.6.so
lrwxrwxrwx 1 khteh root 10 Aug 22 10:38 librt.so -> librt.so.1
-rwxrwxrwx 1 khteh root 18568 Aug 25 05:20 libthread_db-1.0.so
lrwxrwxrwx 1 khteh root 17 Aug 22 10:41 libthread_db.so ->
libthread_db.so.1
-rwxrwxrwx 1 khteh root 9772 Aug 25 05:20 libutil-2.3.6.so
lrwxrwxrwx 1 khteh root 12 Aug 22 10:38 libutil.so -> libutil.so.1
Regards,
Teh
-----Original Message-----
From: Teh Kok How [mailto:khteh at smartbridges.com]
Sent: Tuesday, September 15, 2009 12:01 PM
To: 'busybox at busybox.net'
Subject: ARM GCC-4.2.1 dynamically linked busybox-1.15.0 failed
Hi;
I am using snapgear arm-linux-tools-20070808 with gcc-4.2.1 to build
busybox-1.15.0. Building busybox as statically linked binary is fine.
However, I have never been able to use the dynamically linked busybox
binary. It can't even get to the first C-code of init/init.c. Here is the
failed busybox console log:
<snip>
IP-Config: Complete:
device=eth0, addr=10.0.51.200, mask=255.255.255.0, gw=255.255.255.255,
host=ixdp425, domain=, nis-domain=(none),
bootserver=10.0.51.16, rootserver=10.0.51.16, rootpath=
Looking up port of RPC 100003/2 on 10.0.51.16
Looking up port of RPC 100005/1 on 10.0.51.16
VFS: Mounted root (nfs filesystem) on device 0:13.
Freeing init memory: 108K
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c0027790>] (dump_backtrace+0x0/0x110) from [<c0027c54>]
(dump_stack+0x18/0x1c)
r6:c03ad948 r5:c03c9f84 r4:c03ad948
[<c0027c3c>] (dump_stack+0x0/0x1c) from [<c0044cd8>] (panic+0x54/0x13c)
[<c0044c84>] (panic+0x0/0x13c) from [<c0048530>] (do_exit+0x64/0x684)
r3:00000000 r2:c381a000 r1:00000000 r0:c035bcb0
[<c00484cc>] (do_exit+0x0/0x684) from [<c0048c08>] (do_group_exit+0xb8/0xec)
[<c0048b50>] (do_group_exit+0x0/0xec) from [<c005325c>]
(get_signal_to_deliver+0x39c/0x3f4)
r6:c381a000 r5:0000000b r4:000000dc
[<c0052ec0>] (get_signal_to_deliver+0x0/0x3f4) from [<c0026170>]
(do_signal+0x64/0x53c)
[<c002610c>] (do_signal+0x0/0x53c) from [<c0026674>]
(do_notify_resume+0x2c/0x30)
[<c0026648>] (do_notify_resume+0x0/0x30) from [<c0023e6c>]
(work_pending+0x1c/0x20)
Rebooting in 1 seconds..
Any insight and advice is appreciated. Thanks.
Regards,
Teh
More information about the busybox
mailing list