From: Ralf Baechle <ralf@linux-mips.org>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Christoph Hellwig <hch@sgi.com>,
Andrew Clausen <clausen@melbourne.sgi.com>,
linux-mips@linux-mips.org
Subject: Re: debian's mips userland on mips64
Date: Thu, 23 Jan 2003 06:04:19 +0100 [thread overview]
Message-ID: <20030123060419.B17280@linux-mips.org> (raw)
In-Reply-To: <3E2F5C08.444341D6@melbourne.sgi.com>; from gnb@melbourne.sgi.com on Thu, Jan 23, 2003 at 02:05:44PM +1100
On Thu, Jan 23, 2003 at 02:05:44PM +1100, Greg Banks wrote:
> Actually 32bit strace on a 64bit kernel is working *most* of the time, so
> there must be a 32bit ptrace syscall which is mostly working. But...
>
> 1. There is a problem with tracing rt_sigaction() where the signal set
> argument is being misinterpreted either in ptrace or strace. The
> result is an application buffer overflow in strace which causes it
> to lose track of which processes it's tracing. This may be entirely
> an strace issue but presumably it doesn't happen on 32bit kernels,
> so the fix (when Andrew figures it out) may require strace to know
> whether it's running on a 64bit kernel.
Strace source is pretty evil ...
> 2. At some point in the future there may well be 64bit executables which
> we will want to trace with the 32bit strace. Possibly strace will
> need some sort of modification to dynamically detect whether the
> traced child is 64bit or 32bit.
>
> I'd be very interested to know if anyone's tried running strace on
> a mips64 kernel, in particular strace'ing the scp program.
[...]
ioctl(2, TCGETS, 0x7fff7858) = -1 EINVAL (Invalid argument)
rt_sigaction(SIGPIPE, {0x10000000, [], 0x4055f4}, {SIG_DFL}, 16) = 0
pipe([0, 0]) = 3
pipe([268437928, 721805232]) = 5
pipe([720500616, 2147449192]) = 7
close(3) = 0
[...]
Ralf
next prev parent reply other threads:[~2003-01-23 5:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 7:30 debian's mips userland on mips64 Andrew Clausen
2003-01-22 17:45 ` Christoph Hellwig
2003-01-22 12:45 ` Ralf Baechle
2003-01-22 20:09 ` Christoph Hellwig
2003-01-23 3:05 ` Greg Banks
2003-01-23 5:04 ` Ralf Baechle [this message]
2003-01-22 21:47 ` Greg Lindahl
2003-01-28 7:00 ` Ralf Baechle
[not found] ` <002001c2cba5$ab641320$4437e183@fermi.win.fnal.gov>
2003-02-03 22:56 ` Andrew Clausen
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=20030123060419.B17280@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=clausen@melbourne.sgi.com \
--cc=gnb@melbourne.sgi.com \
--cc=hch@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.