linux-mips
[Top] [All Lists]

Re: explain to me how this works...

To: Jun Sun <jsun@mvista.com>
Subject: Re: explain to me how this works...
From: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 14 Nov 2002 21:12:51 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <20021114120746.E28717@mvista.com>; from jsun@mvista.com on Thu, Nov 14, 2002 at 12:07:46PM -0800
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20021005095335.B4079@lucon.org> <20021113174200.A2874@wumpus.internal.keyresearch.com> <20021114193924.A5610@linux-mips.org> <20021114113045.D1494@wumpus.internal.keyresearch.com> <20021114120746.E28717@mvista.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5.1i
On Thu, Nov 14, 2002 at 12:07:46PM -0800, Jun Sun wrote:

> Look like a good case for using kgdb....

Unlikely to help him.  The return value 4183 of socket that he's observing
is the syscall number of socket(2).  That's making scall_o32.S the first
suspect to look at.

Greg, could this be a case of syscall restarting that you're observing?

  Ralf

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