linux-mips
[Top] [All Lists]

Re: strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...)

To: linux-mips@oss.sgi.com
Subject: Re: strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call)
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Tue, 20 Feb 2001 21:41:25 +0100
In-reply-to: <20010219141130.C17354@cistron.nl>; from wichert@cistron.nl on Mon, Feb 19, 2001 at 02:11:30PM +0100
References: <20010124163048.B15348@paradigm.rfc822.org> <20010124165919.C15348@paradigm.rfc822.org> <20010125165530.B12576@paradigm.rfc822.org> <20010219141130.C17354@cistron.nl>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Mon, Feb 19, 2001 at 02:11:30PM +0100, Wichert Akkerman wrote:

> > sysmips(0x7d1, 0x2ac95d24, 0x1, 0)      = 4149
> 
> FWIW, I've just put code in strace CVS to decode this properly. Looking
> in my (stock Linus) kerneltree I noticed the sys_sysmips code assumes
> it can get away with converting an int to a char*, which seems like a
> wrong assumption to me..
> 
> I don't have my indy up and running at the moment, so the code is
> completely untested. Feedback is welcomed :)

Some versions of the kernel were simply not return anything usefull, so
the the value in $v0 stayed unchanged; 4149 is the syscall number of
sysmips(2).

  Ralf

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