From owner-freebsd-emulation Sat Jan 9 20:46:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27342 for freebsd-emulation-outgoing; Sat, 9 Jan 1999 20:46:12 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27334 for ; Sat, 9 Jan 1999 20:46:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA03149; Sat, 9 Jan 1999 20:42:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901100442.UAA03149@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Marcel Moolenaar , freebsd-emulation@FreeBSD.ORG Subject: Re: sendmsg() not working?! In-reply-to: Your message of "Sat, 09 Jan 1999 14:14:34 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 20:42:23 -0800 From: Mike Smith Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sat, 9 Jan 1999, Marcel Moolenaar wrote: > > > Brian Feldman wrote: > > > > > > I'm working on getting WINE to play properly, using clone() and all, > > > but after resolving how to set the LDT (I added two new LINUX syscalls instead > > > of trying to fix the current Linux ldt syscall's stub), I run into a new block: > > > sendmsg() returns EINVAL (!) for some reason. > > > > Do you have version 1.14 of linux_socket.c? The latest commit added the > > functionality for sendmsg and recvmsg. > > Of course, I am using the very latest of everything. (Running 3.0-CURRENT). > 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. I think that there's something subtly different in the arguments the Linux syscall is passing in. 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) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message