Date: Fri, 17 Oct 1997 16:36:47 -0500 From: Jonathan Lemon <jlemon@americantv.com> To: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE> Cc: Mike Smith <mike@smith.net.au>, freebsd-emulation@FreeBSD.ORG Subject: Re: some observations with xmaple (Maple V4 R5, Linux version) Message-ID: <19971017163647.61997@right.PCS> In-Reply-To: <19971017154439.55593@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Oct 10, 1997 at 03:44:39PM %2B0200 References: <199710150719.JAA10735@gil.physik.rwth-aachen.de> <199710150826.RAA02352@word.smith.net.au> <19971017154439.55593@gil.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971017163647.61997>