qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Bug 1768246 <1768246@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1768246] [NEW] cpu-exec.c:648: cpu_loop_exec_tb: Assertion `use_icount' failed.
Date: Tue, 01 May 2018 16:31:52 +0100	[thread overview]
Message-ID: <87fu3b9ytz.fsf@linaro.org> (raw)
In-Reply-To: <152518111080.22177.382728353135880212.malonedeb@soybean.canonical.com>


John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:

> Public bug reported:
>
> OpenJDK no longer works on qemu-sh4, it previously did after #1735384
> was fixed.
>
> Crash indicates an assertion failure:
>
> (sid-sh4-sbuild)root@nofan:/# java --version
> qemu-sh4-static: /root/qemu/accel/tcg/cpu-exec.c:648: cpu_loop_exec_tb: Assertion `use_icount' failed.
> qemu: uncaught target signal 6 (Aborted) - core dumped
> Aborted
> (sid-sh4-sbuild)root@nofan:/#
>
> Haven't bi-sected the issue yet, but will do so later.

Hmm that's ominous - arguably the assert should be inside the
CONFIG_USER but I'm not sure how you get to the point where icount isn't
< 0 after receiving a TB_EXIT_REQUESTED.

>
> ** Affects: qemu
>      Importance: Undecided
>          Status: New


--
Alex Bennée

  reply	other threads:[~2018-05-01 15:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 13:25 [Qemu-devel] [Bug 1768246] [NEW] cpu-exec.c:648: cpu_loop_exec_tb: Assertion `use_icount' failed John Paul Adrian Glaubitz
2018-05-01 15:31 ` Alex Bennée [this message]
2018-05-01 21:04   ` John Paul Adrian Glaubitz
2018-05-26 14:11     ` John Paul Adrian Glaubitz
2018-08-10 11:52 ` [Qemu-devel] [Bug 1768246] " John Paul Adrian Glaubitz
2018-08-10 21:03 ` Laurent Vivier
2018-10-04 12:38 ` Thomas Huth
2018-12-12  9:21 ` Thomas Huth

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=87fu3b9ytz.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=1768246@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 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).