Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Re: explain to me how this works...
Date: Thu, 14 Nov 2002 19:39:24 +0100	[thread overview]
Message-ID: <20021114193924.A5610@linux-mips.org> (raw)
In-Reply-To: <20021113174200.A2874@wumpus.internal.keyresearch.com>; from lindahl@keyresearch.com on Wed, Nov 13, 2002 at 05:42:00PM -0800

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

  parent reply	other threads:[~2002-11-14 18:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 16:53 gcc 3.2 is available for RedHat 7.3/mips/mipsel H. J. Lu
2002-11-14  1:42 ` explain to me how this works Greg Lindahl
2002-11-14  4:15   ` ilya
2002-11-14 16:10     ` Greg Lindahl
2002-11-14 18:39   ` Ralf Baechle [this message]
2002-11-14 19:30     ` Greg Lindahl
2002-11-14 20:07       ` Jun Sun
2002-11-14 20:12         ` Ralf Baechle
2002-11-14 21:12           ` Greg Lindahl
2002-11-14 21:50             ` Greg Lindahl
2002-11-14 22:27             ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021114193924.A5610@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox