| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Re: explain to me how this works... |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 14 Nov 2002 19:39:24 +0100 |
| In-reply-to: | <20021113174200.A2874@wumpus.internal.keyresearch.com>; from lindahl@keyresearch.com on Wed, Nov 13, 2002 at 05:42:00PM -0800 |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20021005095335.B4079@lucon.org> <20021113174200.A2874@wumpus.internal.keyresearch.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.2.5.1i |
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. Eh? Nothing on MIPS should use socketcall(2); we have all the calls like socket(2), bind(2), connect(2) etc. directly in our syscall table unlike x86 which uses this pointless wrapper for historical reasons. We only have socketcall(2) in the o32 syscall interface but it's a candidate for removal as nothing we still do support and that's glibc 2.0 and higher binaries uses it. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: explain to me how this works..., Greg Lindahl |
|---|---|
| Next by Date: | Re: rsync suggestion, Ralf Baechle |
| Previous by Thread: | Re: explain to me how this works..., Greg Lindahl |
| Next by Thread: | Re: explain to me how this works..., Greg Lindahl |
| Indexes: | [Date] [Thread] [Top] [All Lists] |