[Qemu-devel] [Bug 1812861] [NEW] QEMU in user-mode emulation mode crashes when the user program jumps to an invalid address

[Sergey Lisov]

Public bug reported:

Running this code:

void (*func)() = 0x12345678;

int main()
{
    func();
    return 0;
}

Produces the following output:

qemu-arm-static: /build/qemu-DqynNa/qemu-2.8+dfsg/translate-all.c:175: tb_lock: 
Assertion `!have_tb_lock' failed.
qemu-arm-static: /build/qemu-DqynNa/qemu-2.8+dfsg/translate-all.c:175: tb_lock: 
Assertion `!have_tb_lock' failed.
Segmentation fault

The expected result is as follows:

qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: crash usermode

** Attachment added: "qemu-bug.c"
   https://bugs.launchpad.net/bugs/1812861/+attachment/5231469/+files/qemu-bug.c

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1812861

Title:
  QEMU in user-mode emulation mode crashes when the user program jumps
  to an invalid address

Status in QEMU:
  New

Bug description:
  Running this code:

  void (*func)() = 0x12345678;

  int main()
  {
      func();
      return 0;
  }

  Produces the following output:

  qemu-arm-static: /build/qemu-DqynNa/qemu-2.8+dfsg/translate-all.c:175: 
tb_lock: Assertion `!have_tb_lock' failed.
  qemu-arm-static: /build/qemu-DqynNa/qemu-2.8+dfsg/translate-all.c:175: 
tb_lock: Assertion `!have_tb_lock' failed.
  Segmentation fault

  The expected result is as follows:

  qemu: uncaught target signal 11 (Segmentation fault) - core dumped
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1812861/+subscriptions