[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1516408] Re: sh4: Unsupported syscall: 186

From: Peter Maydell
Subject: [Qemu-devel] [Bug 1516408] Re: sh4: Unsupported syscall: 186
Date: Fri, 17 Jun 2016 15:47:45 -0000

Looks like we fixed this in commit c0d35736323e5b in December, which was
released as part of QEMU 2.6.

** Changed in: qemu
       Status: New => Fix Released

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  sh4: Unsupported syscall: 186

Status in QEMU:
  Fix Released

Bug description:

  I'm currently testing qemu as a possibility to set up a buildd for the
  Debian sh4 port.

  I set up qemu and an sh4 chroot as described in the Debian Wiki [1].
  This seems to be working mostly fine (besides the fact that qemu
  segfaults on an amd64 host while it runs fine on an i386 host, I'll
  file a separate bug report). However, when installing python3.4 in the
  sh4 chroot, qemu repeatedly printed an error message about an
  unimplemented syscall: 186:

  qemu: Unsupported syscall: 186

  From the source code in linux-user/sh4/syscall_nr.h it's apparent that
  186 is defined as

  #define TARGET_NR_sigaltstack   186

  Looking at the implementation part, it becomes obvious that this
  syscall is not enabled for sh4:

  #if defined(TARGET_I386) || defined(TARGET_ARM) || defined(TARGET_MIPS) || \
      defined(TARGET_SPARC) || defined(TARGET_PPC) || defined(TARGET_ALPHA) || \
      defined(TARGET_M68K) || defined(TARGET_S390X) || defined(TARGET_OPENRISC)
          ret = do_sigaltstack(arg1, arg2, get_sp_from_cpustate((CPUArchState 
          goto unimplemented;

  Is there any particular reason why TARGET_NR_sigaltstack is not
  enabled on sh4? If not, could you enable it?


  > [1] https://wiki.debian.org/QemuUserEmulation

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]