Date: Sun, 10 Jan 1999 11:35:39 +0100 From: Marcel Moolenaar <marcel@scc.nl> To: Mike Smith <mike@smith.net.au> Cc: Brian Feldman <green@unixhelp.org>, freebsd-emulation@FreeBSD.ORG Subject: Re: sendmsg() not working?! Message-ID: <3698827B.BBEB4CF3@scc.nl> References: <199901100442.UAA03149@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3698827B.BBEB4CF3>