In <URL:news:local.armlinux> on Sun 02 May, Philip Blundell wrote:
[snip]
> > Also, running ldd on my newly-made hellow ELF executable (or the
> > executables that glibc builds) dies with a register dump. Not an
> > immediate problem.
What I get is:
[root@localhost test]# /usr/arm-new/bin/gcc hellow.c -o hellow
[root@localhost test]# /usr/arm-new/bin/ldd hellow
[166] ld-linux.so.2: branch through zero
pc : [<00000004>]
lr : [<00003f4c>]
sp : 03fffb74 ip : 00020818 fp : 03fffdfc
r10: 000207c4 r9 : 00000001 r8 : 00000002
r7 : 00020938 r6 : 0000bd28 r5 : 00000000 r4 : 00020c50
r3 : 00000001 r2 : 00000188 r1 : 03fffbd0 r0 : 00020c68
Flags: nzCv IRQs on FIQs on Mode USER_32
Function entered at [<000036f0>] from [<00003668>]
ldd: /usr/arm-new/lib/ld-linux.so.2 exited with unknown exit code (132)
I get the same sort of branch through zero if I run `/lib/ld-linux.so.2' on
its own without any parameters.
> > Incidentally, Debian appears to use a separate ld.so from the one in
> > glibc. Why's that?
>
> You might be thinking of the ld.so.1 which is used for libc4 binaries, or
> the ld-linux.so.1 which is used for libc5 binaries on other platforms.
> Neither of these will work with code compiled against glibc, nor will the
> corresponding ldd.
No, I'm thinking of the ld-linux.so.2 on Debian 2.1, which has a separate
source package to glibc. The reason I mention it is that ldd on a Debian
box is an ELF executable, whereas the one installed by glibc is a shell
script which runs `/usr/arm-new/lib/ld-linux.so.2'.
--
Mark Seaborn
- [EMAIL PROTECTED] - http://www.argonet.co.uk/users/mseaborn/ -
``I owe a lot to my parents, especially my mother and
my father'' -- Greg Norman
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
