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 > > > > > >
