All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Cowgill <jcowgill@debian.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1673976] Re: linux-user clone() can't handle glibc posix_spawn() (causes locale-gen to assert)
Date: Wed, 22 Nov 2017 15:30:10 -0000	[thread overview]
Message-ID: <151136461101.18190.14465747737982475589.malone@gac.canonical.com> (raw)
In-Reply-To: 20170318142657.21676.52259.malonedeb@chaenomeles.canonical.com

Sorry, this is probably the commit that broke things (not the one above). I was added in glibc 2.25:
https://sourceware.org/git/?p=glibc.git;a=commit;h=4b4d4056bb154603f36c6f8845757c1012758158

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1673976

Title:
  linux-user clone() can't handle glibc posix_spawn() (causes locale-gen
  to assert)

Status in QEMU:
  New

Bug description:
  I'm running a command (locale-gen) inside of an armv7h chroot mounted
  on my x86_64 desktop by putting qemu-arm-static into /usr/bin/ of the
  chroot file system and I get a core dump.

  locale-gen
  Generating locales...
    en_US.UTF-8...localedef: ../sysdeps/unix/sysv/linux/spawni.c:360: __spawnix: Assertion `ec >= 0' failed.
  qemu: uncaught target signal 6 (Aborted) - core dumped
  /usr/bin/locale-gen: line 41:    34 Aborted                 (core dumped) localedef -i $input -c -f $charset -A /usr/share/locale/locale.alias $locale

  I've done this same thing successfully for years, but this breakage
  has appeared some time in the last 3 or so months. Possibly with the
  update to qemu version 2.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1673976/+subscriptions

  parent reply	other threads:[~2017-11-22 15:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 14:26 [Qemu-devel] [Bug 1673976] [NEW] core dump l3iggs
2017-09-20 20:10 ` [Qemu-devel] [Bug 1673976] " Matheus Izvekov
2017-09-21  3:38 ` Thomas Huth
2017-10-02 18:36 ` Alchemist
2017-10-02 18:37 ` Alchemist
2017-10-03  5:30 ` Thomas Huth
2017-10-16 18:04 ` Dominique Belhachemi
2017-10-16 19:23 ` Dominique Belhachemi
2017-11-03 16:34 ` [Qemu-devel] [Bug 1673976] Re: locale-gen dumps core run under arm-linux-user on x86-64 host Peter Maydell
2017-11-06 19:14 ` Peter Maydell
2017-11-07 15:30 ` Peter Maydell
2017-11-20 17:33 ` [Qemu-devel] [Bug 1673976] Re: linux-user clone() can't handle glibc posix_spawn() (causes locale-gen to assert) l3iggs
2017-11-20 18:00 ` Peter Maydell
2017-11-20 18:36 ` Peter Maydell
2017-11-22 15:01 ` James Cowgill
2017-11-22 15:26 ` James Cowgill
2017-11-22 15:30 ` James Cowgill [this message]
2017-11-22 16:52 ` Peter Maydell
2017-11-26 20:38 ` John Paul Adrian Glaubitz
2017-12-01 12:03 ` John Paul Adrian Glaubitz
2018-02-27 20:09 ` Éric Hoffman
2018-02-27 21:19 ` Peter Maydell
2018-02-28 15:16 ` Éric Hoffman
2018-02-28 15:39 ` Peter Maydell
2018-03-02 20:59 ` Éric Hoffman
2018-03-03 11:56 ` Peter Maydell
2018-03-05 13:35 ` Éric Hoffman
2018-03-05 14:02 ` Peter Maydell
2018-03-23 18:37 ` Éric Hoffman
2018-03-23 19:07 ` Peter Maydell
2020-12-04 22:05 ` Davide Palma
2021-05-05  6:56 ` Thomas Huth

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=151136461101.18190.14465747737982475589.malone@gac.canonical.com \
    --to=jcowgill@debian.org \
    --cc=1673976@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.