| To: | David Daney <ddaney@avtrex.com> |
|---|---|
| Subject: | Re: Bug in the syscall tracing code |
| From: | "Gleb O. Raiko" <raiko@niisi.msk.ru> |
| Date: | Fri, 07 Oct 2005 11:50:43 +0400 |
| Cc: | Thiemo Seufer <ths@networkno.de>, linux-mips@linux-mips.org |
| In-reply-to: | <43459374.5080802@avtrex.com> |
| Organization: | NIISI RAN |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <43455D2D.1010901@niisi.msk.ru> <20051006205308.GB31717@hattusa.textio> <43459374.5080802@avtrex.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mozilla Thunderbird 1.0.7 (Windows/20050923) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Bug in the syscall tracing code, Gleb O. Raiko |
|---|---|
| Next by Date: | Is CONFIG_CPU_MIPS32_R2 workable?, colin |
| Previous by Thread: | Re: Bug in the syscall tracing code, David Daney |
| Next by Thread: | Re: Bug in the syscall tracing code, David Daney |
| Indexes: | [Date] [Thread] [Top] [All Lists] |