From: "Dr. David Alan Gilbert" <883133@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 883133] Re: qemu on ARM hosts asserts due to code buffer/libc heap conflict
Date: Thu, 15 Dec 2011 10:21:24 -0000 [thread overview]
Message-ID: <20111215102125.30759.88506.malone@wampee.canonical.com> (raw)
In-Reply-To: 20111028150403.31257.25788.malonedeb@chaenomeles.canonical.com
Fix pushed into QEMU upstream today.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/883133
Title:
qemu on ARM hosts asserts due to code buffer/libc heap conflict
Status in QEMU:
New
Status in Linaro QEMU:
In Progress
Bug description:
On ARM hosts qemu (about half the time) asserts on startup:
qemu-system-i386: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) -
__builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
This turns out to be because code_gen_alloc() is using mmap(MAP_FIXED)
to map the code buffer at address 0x01000000UL, which is in the area
glibc happens to be using for its heap. This tends to make the next
malloc() abort, although occasionally the stars align and we pass that
and fail weirdly later on.
I suspect we need to drop the MAP_FIXED requirement and fix the TCG code to cope with emitting code for longer-range
branches for calls to host fns etc (calls/branches within the generated code should be ok to keep using the short-range
branch insn I think). There is already no guarantee that the generated code and the host C code are within short
branch range of each other...
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/883133/+subscriptions
next prev parent reply other threads:[~2011-12-15 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111028150403.31257.25788.malonedeb@chaenomeles.canonical.com>
2011-12-01 20:11 ` [Qemu-devel] [Bug 883133] Re: qemu on ARM hosts asserts due to code buffer/libc heap conflict Natalia Portillo
2011-12-09 18:50 ` Dr. David Alan Gilbert
2011-12-15 10:21 ` Dr. David Alan Gilbert [this message]
2011-12-15 22:56 ` Peter Maydell
2012-01-04 15:16 ` Peter Maydell
2012-01-05 0:58 ` Michael Hope
2012-01-05 16:03 ` Peter Maydell
2012-01-12 10:12 ` Peter Maydell
2012-07-10 14:54 ` Peter Maydell
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=20111215102125.30759.88506.malone@wampee.canonical.com \
--to=883133@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.