Re: /usr/bin/m4: internal error detected
On 12/01/2017 01:18 PM, Andreas Schwab wrote:
This isn't a bug in m4 or anything architecture-specific, it's a regression
that was introduced by an upstream change in glibc  and mainly affects
qemu-user which we are using for m68k and sh4 .
It's a bug in qemu-linux-user, which ignores CLONE_VFORK, turning vfork
into fork. This breaks the expected semantics of vfork (VM sharing and
blocking the child until exec).
Yes, I wasn't really arguing that it's a bug in QEMU as Adhemerval had already
explained. The problem was just that apparently resolving the issue in
QEMU isn't trivial as Peter Maydell mentioned in .
That's why I was looking for a workaround. However, I have re-tested Florian's
patch and it works for me now, it didn't when I tested it for the first time.
So, we have a workaround for the time being until the bug is resolved in QEMU.
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - firstname.lastname@example.org
`. `' Freie Universitaet Berlin - email@example.com
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913