On Tue, May 24, 2011 at 10:42 PM, Artyom Tarasenko <atar4q...@gmail.com> wrote:
> Should it be possible to use dynamically linked binaries under
> sparc*-linux-user?
> Under qemu-system-sparc the Debian 4.08r1 initrd works fine, but:
>
> master$ sparc-linux-user/qemu-sparc -strace -L
> ../debian-4.08r1-initrd/ ../debian-4.08r1-initrd/bin/busybox
> 14004 uname(0x409ffbae) = 0
> 14004 brk(NULL) = 0x00063000
> 14004 access("/etc/ld.so.nohwcap",F_OK) = -1 errno=2 (No such file or
> directory)
> 14004 mmap(NULL,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0)
> = 0x40a2c000
> 14004 access("/etc/ld.so.preload",R_OK) = -1 errno=2 (No such file or
> directory)
> 14004 open("/etc/ld.so.cache",O_RDONLY) = 3
> 14004 fstat64(3,0x409ff500) = 0
> 14004 mmap(NULL,195479,PROT_READ,MAP_PRIVATE,3,0) = 0x40a2d000
> 14004 close(3) = 0
> Segmentation fault
>
> The strange thing here is that it loads ld.so.cache. The guest fs
> doesn't have it, but the host does:
>
> master$ ll ../../debian-4.08r1-initrd/etc/ld.so.cache /etc/ld.so.cache
> ls: cannot access ../../debian-4.08r1-initrd/etc/ld.so.cache: No such
> file or directory
> -rw-r--r--. 1 root root 195479 2011-03-17 13:48 /etc/ld.so.cache
>
> Isn't this wrong?
I'm not sure. It could be possible to construct a blacklist of host
files that may not be accessible or visible to the guest but that
wouldn't very robust either. Chrooting into a 100% guest architecture
system should work better.
