From: "Rafael Espíndola" <rafael.espindola@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bug in ARM thumb usermode emulation
Date: Tue, 19 Sep 2006 17:36:56 -0300 [thread overview]
Message-ID: <564d96fb0609191336j23943104w506d409e8fbc77ba@mail.gmail.com> (raw)
In-Reply-To: <200609182117.00519.paul@codesourcery.com>
On 9/18/06, Paul Brook <paul@codesourcery.com> wrote:
> TLS and multithreaded applications are known to not work with usermode
> emulation.
It looks like this is a memory corruption problem and the assert that
fails is just a coincidence!
I started to remove code from python to find what triggers the assert.
I ended up with an empty main linked only with libc!
I new version of the chroot is available at
http://www.maemo.org.br/platform/rafael/qemu-bug.tar.bz2
Any ideas on how to debug this?
> Paul
Thanks,
Rafael
next prev parent reply other threads:[~2006-09-19 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 20:05 [Qemu-devel] bug in ARM thumb usermode emulation Rafael Espíndola
2006-09-18 20:16 ` Paul Brook
2006-09-18 20:43 ` Rafael Espíndola
2006-09-18 20:56 ` Paul Brook
2006-09-19 20:36 ` Rafael Espíndola [this message]
2006-09-29 10:59 ` Rafael Espíndola
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=564d96fb0609191336j23943104w506d409e8fbc77ba@mail.gmail.com \
--to=rafael.espindola@gmail.com \
--cc=paul@codesourcery.com \
--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 NNTP newsgroup(s).