From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53595) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDw7g-0006v4-EG for qemu-devel@nongnu.org; Fri, 17 Jun 2016 11:55:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bDw7c-0001Ka-6s for qemu-devel@nongnu.org; Fri, 17 Jun 2016 11:55:55 -0400 Received: from indium.canonical.com ([91.189.90.7]:39227) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDw7c-0001KN-1l for qemu-devel@nongnu.org; Fri, 17 Jun 2016 11:55:52 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1bDw7a-0005YL-Qh for ; Fri, 17 Jun 2016 15:55:51 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 9E1542E80CE for ; Fri, 17 Jun 2016 15:55:50 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 17 Jun 2016 15:47:45 -0000 From: Peter Maydell Reply-To: Bug 1516408 <1516408@bugs.launchpad.net> Sender: bounces@canonical.com References: <20151115171321.16209.6583.malonedeb@soybean.canonical.com> Message-Id: <20160617154746.2401.70982.malone@chaenomeles.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1516408] Re: sh4: Unsupported syscall: 186 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Looks like we fixed this in commit c0d35736323e5b in December, which was released as part of QEMU 2.6. ** Changed in: qemu Status: New =3D> Fix Released -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1516408 Title: sh4: Unsupported syscall: 186 Status in QEMU: Fix Released Bug description: Hello! 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_OPENR= ISC) ret =3D do_sigaltstack(arg1, arg2, get_sp_from_cpustate((CPUArchS= tate *)cpu_env)); break; #else goto unimplemented; #endif Is there any particular reason why TARGET_NR_sigaltstack is not enabled on sh4? If not, could you enable it? Thanks, Adrian > [1] https://wiki.debian.org/QemuUserEmulation To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1516408/+subscriptions