On Sat, 8 Dec 2018, John Paul Adrian Glaubitz wrote: > > This seems to affect qemu-user only while the lock-up problem with dash > occurs on qemu-system only. > > Finn, did you verify the lock-up problem on real hardware by any chance? >
I don't have my 68k hardware with me at the moment. > Just to make sure the lock-up is not a qemu bug. > Well, if it's a qemu bug then it's also an aranym bug. If you want to reproduce on elgar, you only need 3 files: # ls -lR .: total 8 drwxr-xr-x 2 root root 4096 Dec 3 07:31 bin drwxr-xr-x 3 root root 4096 Nov 28 22:42 lib ./bin: total 112 -rwxr-xr-x 1 root root 108220 Dec 3 07:31 dash lrwxrwxrwx 1 root root 4 Dec 3 07:31 sh -> dash ./lib: total 4 lrwxrwxrwx 1 root root 25 Nov 28 22:42 ld.so.1 -> m68k-linux-gnu/ld-2.28.so drwxr-xr-x 2 root root 4096 Dec 3 07:31 m68k-linux-gnu ./lib/m68k-linux-gnu: total 1412 -rwxr-xr-x 1 root root 120008 Nov 28 22:42 ld-2.28.so lrwxrwxrwx 1 root root 10 Nov 28 22:42 ld.so.1 -> ld-2.28.so -rwxr-xr-x 1 root root 1314040 Nov 28 22:42 libc-2.28.so lrwxrwxrwx 1 root root 12 Nov 28 22:42 libc.so.6 -> libc-2.28.so # chroot . /bin/sh # /bin/sh -c foo /bin/sh: 1: foo: not found At this point dash has hung. If you strace that process from outside the chroot, you can see it looping around wait4() = -1 ECHILD. -- > Adrian > >
