From: Ralf Baechle <ralf@linux-mips.org>
To: Ton Truong <ttruong@broadcom.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Member sc_sigset gone in latest 2.6.12-rc5 breaks strace.
Date: Thu, 9 Jun 2005 23:01:47 +0100 [thread overview]
Message-ID: <20050609220147.GA4802@linux-mips.org> (raw)
In-Reply-To: <20050609204937.GK4927@linux-mips.org>
On Thu, Jun 09, 2005 at 09:49:37PM +0100, Ralf Baechle wrote:
> > I see that in the rc5 update, MIPS codes have now dropped
> > sc_sigset[4] from struct sigcontext, defined in asm-mips/sigcontext.h. I'd
> > appreciate it if someone provide a brief summary of what needs to be changed
> > for strace to compile or where I can find an strace port that work with the
> > new MIPS codes?
>
> sc_sigset and the other members that were changed have been unused by the
> kernel since a very, very long time so whatever strace may have done with
> that field was probably bogus.
>
> Thanks for reporting, something I'm going to look at tomorrow.
Ok, it was just too trivial. Here's an untested patch.
Ralf
signal.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: strace-cvs/signal.c
===================================================================
--- strace-cvs.orig/signal.c 2005-06-09 22:56:14.000000000 +0100
+++ strace-cvs/signal.c 2005-06-09 22:56:27.000000000 +0100
@@ -1420,7 +1420,7 @@
if (umove(tcp, sp, &sc) < 0)
return 0;
tcp->u_arg[0] = 1;
- tcp->u_arg[1] = sc.sc_sigset;
+ tcp->u_arg[1] = &sc + 1;
} else {
tcp->u_rval = tcp->u_error = 0;
if(tcp->u_arg[0] == 0)
next prev parent reply other threads:[~2005-06-13 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050605035727Z8225003-1340+8177@linux-mips.org>
2005-06-06 12:16 ` CVS Update@linux-mips.org: linux Ralf Baechle
2005-06-09 17:37 ` Member sc_sigset gone in latest 2.6.12-rc5 breaks strace Ton Truong
2005-06-09 20:49 ` Ralf Baechle
2005-06-09 22:01 ` Ralf Baechle [this message]
2005-06-14 16:06 ` 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=20050609220147.GA4802@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=ttruong@broadcom.com \
/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