From owner-freebsd-emulation Fri Oct 17 14:38:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA10043 for emulation-outgoing; Fri, 17 Oct 1997 14:38:07 -0700 (PDT) (envelope-from owner-freebsd-emulation) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA10023 for ; Fri, 17 Oct 1997 14:37:53 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id QAA07353; Fri, 17 Oct 1997 16:37:19 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id QAA06322; Fri, 17 Oct 1997 16:36:47 -0500 Message-ID: <19971017163647.61997@right.PCS> Date: Fri, 17 Oct 1997 16:36:47 -0500 From: Jonathan Lemon To: Christoph Kukulies Cc: Mike Smith , freebsd-emulation@FreeBSD.ORG Subject: Re: some observations with xmaple (Maple V4 R5, Linux version) References: <199710150719.JAA10735@gil.physik.rwth-aachen.de> <199710150826.RAA02352@word.smith.net.au> <19971017154439.55593@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19971017154439.55593@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Oct 10, 1997 at 03:44:39PM +0200 Sender: owner-freebsd-emulation@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 10, 1997 at 03:44:39PM +0200, Christoph Kukulies wrote: > I'm including a kdump excerpt hoping that someone knowing of the > subtleties of old.receiv .. Note that ktrace just records the syscall numbers, and that kdump prints these out using a BSD syscall mapping. This means that the names printed out for a Linux program are completely bogus. > 19073 xmaplev4 CALL old.recv(0x1,0xefbfd2d4) > 19073 xmaplev4 RET old.recv 3 > 19073 xmaplev4 CALL old.recv(0xe,0xefbfd2c4) > 19073 xmaplev4 RET old.recv -1 errno -22 Unknown error: -22 old.recv == syscall #102 == linux_socketcall. There are only 4 sub-routines that can return EINVAL (-22): linux_socket, linux_socketpair, linux_setsockopt, linux_getsockopt. I'd suggest modifying these routines (in linux/linux_socket.c) to print out the parameters that is causing it to crash. (Assuming, of course, the above error return is causing the crash) -- Jonathan