All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bernhard M. Wiedemann" <bwiedemann@suse.de>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, riku.voipio@iki.fi,
	paul@codesourcery.com, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] ARM brk bug
Date: Mon, 27 Feb 2012 16:16:59 +0100	[thread overview]
Message-ID: <4F4B9E6B.2020405@suse.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I found that running a debian arm5 bash with qemu runs into varying
problems with -R but works without. Also works fine on both armv5 and
armv7hf hardware.


This happened with both master and 1.0 builds:

curl www.zq1.de/~bernhard/temp/debian-bash-bug-nss-minimal.tar.gz |\
  tar xz
cd debian-bash-bug-nss-minimal
path/to/qemu/arm-linux-user/qemu-arm -R 500M -L . bin/bash
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault


with chroot and our openSUSE qemu-arm-binfmt (which only does some
argv[0] magic) I saw it working after rm lib/libnss*

but otherwise it failed with messages like
bash: xmalloc: ../bash/variables.c:1971: cannot allocate 2 bytes (8192
bytes allocated)


Ciao
Bernhard M.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9LnmsACgkQSTYLOx37oWT6FgCdEgIriKRVmwkaMQU6jBGN/ABP
s/EAn1cZj4KytK9iC3i6EqqfIXFyEUVX
=DCV8
-----END PGP SIGNATURE-----

             reply	other threads:[~2012-02-27 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 15:16 Bernhard M. Wiedemann [this message]
2012-02-27 15:32 ` [Qemu-devel] ARM brk bug Peter Maydell
2012-02-27 17:03   ` Bernhard M. Wiedemann
2012-02-27 17:04     ` Peter Maydell
2012-03-02 17:49 ` Peter Maydell
2012-03-03  1:42   ` Alexander Graf
2012-03-03 21:02   ` Alexander Graf
2012-03-03 21:05     ` Alexander Graf
2012-03-03 21:17     ` Paul Brook
2012-03-03 22:08       ` Andreas Schwab
2012-03-03 21:23     ` malc

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=4F4B9E6B.2020405@suse.de \
    --to=bwiedemann@suse.de \
    --cc=agraf@suse.de \
    --cc=paul@codesourcery.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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.