All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Michael Clark <mjc@sifive.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu:handle_cpu_signal received signal outside vCPU context
Date: Wed, 30 May 2018 11:02:55 +0200	[thread overview]
Message-ID: <mvmmuwh7by8.fsf@suse.de> (raw)
In-Reply-To: <CAHNT7NuOLVGyodcJ98ruM5t+m1s=in07dXfNp_77=vTOb=1yhQ@mail.gmail.com> (Michael Clark's message of "Mon, 19 Mar 2018 15:10:46 -0700")

On Mär 19 2018, Michael Clark <mjc@sifive.com> wrote:

> On Mon, Mar 19, 2018 at 9:17 AM, Andreas Schwab <schwab@suse.de> wrote:
>
>> I'm seeing this error while building gedit for riscv64 with linux-user
>> emulation:
>>
>> $ LD_LIBRARY_PATH=gedit/.libs qemu-riscv64 gedit/.libs/gedit
>> --introspect-dump=/tmp/tmp-introspectnj0xla07/functions.txt,
>> /tmp/tmp-introspectnj0xla07/dump.xml
>> qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003d7d5
>> qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60106a16
>>
>
> Thanks. I can see this code in accel/tcg/user-exec.c
>
> It would be nice if that log message included the signal number. I wonder
> if we are getting a SIGSEGV. I also wonder what thread is actually
> running...

A native build doesn't see any issues, so this looks like a genuine qemu
bug.

> I wonder what is the best way for me to reproduce on my side... a tarball
> with binaries that I can use to trigger the fault?

There are some images under
<http://download.opensuse.org/repositories/openSUSE:/Factory:/RISCV/images/>
that can be used as a base.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

      parent reply	other threads:[~2018-05-30  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 16:17 [Qemu-devel] qemu:handle_cpu_signal received signal outside vCPU context Andreas Schwab
2018-03-19 22:10 ` Michael Clark
2018-03-20  9:10   ` Andreas Schwab
2018-05-30  9:02   ` Andreas Schwab [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=mvmmuwh7by8.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=mjc@sifive.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 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.