From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug] qemu-sparc64 broken
Date: Fri, 06 Sep 2013 08:20:46 -0700 [thread overview]
Message-ID: <5229F2CE.6080509@twiddle.net> (raw)
In-Reply-To: <CAFEAcA8n43Q7sZfwy6UKPrEFCiYPY8siQ9ic7pMs2MYzK8rX+w@mail.gmail.com>
On 09/06/2013 08:15 AM, Peter Maydell wrote:
> On 6 September 2013 16:12, Richard Henderson <rth@twiddle.net> wrote:
>> On 09/05/2013 09:53 PM, Stefan Weil wrote:
>>> After lots of SIGSEGV, the program indeed finishes successfully,
>>> so my report was wrong - SIGSEGV is not a fatal signal for sparc64.
>>> That's interesting - thank you for this information.
>>
>> It's not just sparc64.
>>
>> That's changed page detection, for determining when to invalidate
>> translation blocks. For self-modifying code, and more.
>
> Yeah, but in practice sparc64 does this a huge number of
> times on simple binaries in a way that other linux-user
> guests I looked at just don't. Presumably it's just that
> gcc has for some reason put writable data next to code
> for that target.
It's the (old?) PLT scheme for sparc -- it modifies code on linking.
If you use LD_BIND_NOW=1 it can help speed things up when debugging.
r~
prev parent reply other threads:[~2013-09-06 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 20:35 [Qemu-devel] [Bug] qemu-sparc64 broken Stefan Weil
2013-09-05 21:32 ` Peter Maydell
2013-09-06 4:53 ` Stefan Weil
2013-09-06 15:12 ` Richard Henderson
2013-09-06 15:15 ` Peter Maydell
2013-09-06 15:20 ` Richard Henderson [this message]
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=5229F2CE.6080509@twiddle.net \
--to=rth@twiddle.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.