linux-mips
[Top] [All Lists]

Re: explain to me how this works...

To: linux-mips@linux-mips.org
Subject: Re: explain to me how this works...
From: Greg Lindahl <lindahl@keyresearch.com>
Date: Thu, 14 Nov 2002 08:10:43 -0800
In-reply-to: <20021114041538.GB5986@gateway.total-knowledge.com>; from ilya@theIlya.com on Wed, Nov 13, 2002 at 08:15:38PM -0800
Mail-followup-to: linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20021005095335.B4079@lucon.org> <20021113174200.A2874@wumpus.internal.keyresearch.com> <20021114041538.GB5986@gateway.total-knowledge.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5.1i
I saw that a long time ago. sys_socket and sys_socketcall seem
to be written just like all the other syscalls that return an int.

> see arch/mips64/kernel/linux32.c
> 
> On Wed, Nov 13, 2002 at 05:42:00PM -0800, Greg Lindahl wrote:
> > I have a 64-bit kernel and O32 userland.
> > 
> > I notice that arping gets confused because the syscall socket() is
> > returning 4183 instead of a reasonable value like 3... if strace()
> > isn't lying to me.
> > 
> > How do I debug this? The O32 userland calls through the socketcall()
> > syscall. It looks OK.
> > 
> > greg
> > 
> > 
> > 



<Prev in Thread] Current Thread [Next in Thread>