qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Stefan Weil <sw@weilnetz.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug] qemu-sparc64 broken
Date: Fri, 06 Sep 2013 08:12:30 -0700	[thread overview]
Message-ID: <5229F0DE.7040308@twiddle.net> (raw)
In-Reply-To: <52295FD4.2030207@weilnetz.de>

On 09/05/2013 09:53 PM, Stefan Weil wrote:
> Am 05.09.2013 23:32, schrieb Peter Maydell:
>> On 5 September 2013 21:35, Stefan Weil <sw@weilnetz.de> wrote:
>>> In a first analysis of this, I noticed that it is impossible to run
>>> qemu-sparc64
>>> under gdb (raised fatal signal).
>> You probably just need to let the signals go through to
>> the target... I noticed that it had a tendency to do lots
>> of (presumably safely handled) segfaulting while running;
>> didn't look at why this happens.
> 
> 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.


r~

  reply	other threads:[~2013-09-06 15:12 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 [this message]
2013-09-06 15:15       ` Peter Maydell
2013-09-06 15:20         ` Richard Henderson

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=5229F0DE.7040308@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 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).