Date: Sat, 09 Jan 1999 20:42:23 -0800 From: Mike Smith <mike@smith.net.au> To: Brian Feldman <green@unixhelp.org> Cc: Marcel Moolenaar <marcel@scc.nl>, freebsd-emulation@FreeBSD.ORG Subject: Re: sendmsg() not working?! Message-ID: <199901100442.UAA03149@dingo.cdrom.com> In-Reply-To: Your message of "Sat, 09 Jan 1999 14:14:34 EST." <Pine.BSF.4.05.9901091401480.304-100000@janus.syracuse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901100442.UAA03149>