There has been some motion on this by Aladjev Andrew. I will butcher
the explanation of his approach if I try, but it is described in the
following bugs. I have no idea of the schedule, or even possibility of
adoption; it seems to still be in proof-of-concept phase.
GLIBC bug (see last several p
After studying linux-user/syscall.c a bit, would it be possible to work
around this issue by doing something like the following:
Add a new #define EMULATE_GETDENTS64_WITH_GETDENTS, and enable this iff
we have getdents, and the target is 32, while the host is 64 bits.
Something similar, but complem
https://lkml.org/lkml/2018/12/27/155
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1805913
Title:
readdir() returns NULL (errno=EOVERFLOW) for 32-bit user-static qemu
on 64-bit host
Status in QE
I was also hit by this on Gentoo with a 64bit host running 32bit static
chroot (arm). If it matters at all, I saw it after upgrading the 32bit
arm chroot to glibc-2.28, while the host was still on 2.27.
Downgrading again hides the issue. Upgrading the host to glibc 2.28,
but keeping the chroot a
Unfortunately, no dice
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1765970
Title:
qemu-arm (user mode) segfaults in uclibc-ng chroot after upgrade to
2.11.x
Status in QEMU:
New
Bug descript
Public bug reported:
I use a qemu-user chroot + binfmt to build software targetting a
raspberry pi. After upgrading from qemu-2.10.1 to 2.11.1 (Gentoo host),
I noticed that on my uclibc-ng chroot qemu-arm will segfault when
running python and importing the portage module.
I have bisected qemu do