From: Andreas Schwab <schwab@linux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
bug-m4@gnu.org, debian-superh@lists.debian.org,
libc-alpha@sourceware.org,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: /usr/bin/m4: internal error detected
Date: Fri, 01 Dec 2017 12:19:00 -0000 [thread overview]
Message-ID: <871ske63pu.fsf@linux-m68k.org> (raw)
In-Reply-To: <f5f44f70-d274-e7a6-618e-8906f58a9073@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Fri, 1 Dec 2017 10:51:11 +0100")
On Dez 01 2017, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> 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 [1] and mainly affects
> qemu-user which we are using for m68k and sh4 [2].
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).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-12-01 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87po7zrq65.fsf@fifthhorseman.net>
2017-12-01 9:51 ` John Paul Adrian Glaubitz
2017-12-01 10:40 ` Florian Weimer
2017-12-01 11:57 ` Adhemerval Zanella
2017-12-01 11:58 ` John Paul Adrian Glaubitz
2017-12-01 12:35 ` Florian Weimer
2017-12-01 12:19 ` Andreas Schwab [this message]
2017-12-01 12:22 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871ske63pu.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=bug-m4@gnu.org \
--cc=debian-superh@lists.debian.org \
--cc=dkg@fifthhorseman.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=libc-alpha@sourceware.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).