From owner-freebsd-emulation Sun Jan 10 02:36:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29680 for freebsd-emulation-outgoing; Sun, 10 Jan 1999 02:36:50 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29675 for ; Sun, 10 Jan 1999 02:36:46 -0800 (PST) (envelope-from marcel@scc.nl) Received: from scones.sup.scc.nl (i458.ztm.euronet.nl [194.134.67.179]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id LAA27077; Sun, 10 Jan 1999 11:36:13 +0100 (MET) Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.1/8.9.1) with ESMTP id LAA29194; Sun, 10 Jan 1999 11:35:39 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3698827B.BBEB4CF3@scc.nl> Date: Sun, 10 Jan 1999 11:35:39 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: Brian Feldman , freebsd-emulation@FreeBSD.ORG Subject: Re: sendmsg() not working?! References: <199901100442.UAA03149@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > There's no real extra functionality, sendmsg in linux is exactly the same, > > binary-compatible with that of FreeBSD. When groping through the kernel to > > find out why sendmsg() can return EINVAL, I can't seem to find a reason. > > I've seen this before; there's definitely a couple of reasons why it > can return that. Sounds like you already know exactly what those reasons are :-) > I think that there's something subtly different in the arguments the > Linux syscall is passing in. The obvious one I know of (see my previous mail) is the flags field in the msghdr struct. That's it. If there's more, let me know. > You shouldn't have any trouble trapping the Linux sendmsd call and using > kdb-remote to step through the kernel until you find the problem though. 8) If I hadn't had the resources so remotely, yes :-) Just one question. Is it save to assume there is no problem with the native FreeBSD syscall? To put it differently; Is it wise to focus on the subtle differences of the Linux syscall? marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message