From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: David Daney <ddaney@avtrex.com>
Cc: Thiemo Seufer <ths@networkno.de>, linux-mips@linux-mips.org
Subject: Re: Bug in the syscall tracing code
Date: Fri, 07 Oct 2005 11:50:43 +0400 [thread overview]
Message-ID: <434628D3.9050307@niisi.msk.ru> (raw)
In-Reply-To: <43459374.5080802@avtrex.com>
David Daney wrote:
> That is the conclusion I came to in:
>
> http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=4207C3E0.7070405%40avtrex.com
Saving in the PT_SCRATCH area (pad0 in C) was a solution for 2.4.
Unfortunately, syscall arguments are stored there (and that's why pad0
exists in pt_regs after all). So, using PT_SCRATCH as a temporary
storage for t2 will break tracing syscalls with more than 4 args for o32
ABI.
Regards,
Gleb.
next prev parent reply other threads:[~2005-10-07 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 17:21 Bug in the syscall tracing code Gleb O. Raiko
2005-10-06 20:53 ` Thiemo Seufer
2005-10-06 21:13 ` David Daney
2005-10-07 7:50 ` Gleb O. Raiko [this message]
2005-10-07 15:26 ` David Daney
2005-10-07 7:43 ` Gleb O. Raiko
2005-10-07 12:44 ` Gleb O. Raiko
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=434628D3.9050307@niisi.msk.ru \
--to=raiko@niisi.msk.ru \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
/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