From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix ptrace compat wrapper for fpu register access
Date: Mon, 30 Mar 2009 11:17:19 +0200 [thread overview]
Message-ID: <m2vdpr2wv4.fsf@igel.home> (raw)
In-Reply-To: <13580.1238371079@neuling.org> (Michael Neuling's message of "Mon, 30 Mar 2009 10:57:59 +1100")
Michael Neuling <mikey@neuling.org> writes:
> So if you're looking fixing 32 bit apps ptracing 64 bit apps, does that
> mean we can get a single 32 bit GDB that'll ptrace both 64 and 32 bit
> apps?
Currently gdb only supports 32x64 debugging for the SPU.
>> @@ -263,7 +263,8 @@ long compat_arch_ptrace(struct task_struct *child, compat
> _long_t request,
>> ret = ptrace_put_reg(child, numReg, freg);
>> } else {
>> flush_fp_to_thread(child);
>> - ((unsigned int *)child->thread.regs)[index] = data;
>> + ((unsigned int *)child->thread.regs)
>> + [FPRINDEX(index)] = data;
>
> This index is into the ptregs structure not the fpr. I'm not sure the
> FPRINDEX macro is applicable here.
You're right, this hunk is bogus. But indexing off thread.regs is
totally bogus as well. I think what was intented is this:
@@ -263,7 +263,9 @@ long compat_arch_ptrace(struct task_stru
ret = ptrace_put_reg(child, numReg, freg);
} else {
flush_fp_to_thread(child);
- ((unsigned int *)child->thread.regs)[index] = data;
+ ((unsigned int *)child->thread.fpr)
+ [TS_FPRWIDTH * (numReg - PT_FPR0) * 2 +
+ index % 2] = data;
ret = 0;
}
break;
But gdb does not actually use PPC_PTRACE_POKEUSR_3264.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-03-30 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 17:56 [PATCH] Fix ptrace compat wrapper for fpu register access Andreas Schwab
2009-03-29 23:57 ` Michael Neuling
2009-03-30 9:17 ` Andreas Schwab [this message]
2009-03-30 9:52 ` Michael Neuling
2009-03-30 11:11 ` Andreas Schwab
2009-03-30 22:53 ` Michael Neuling
2009-04-06 6:48 ` Michael Neuling
2009-04-06 6:59 ` Michael Neuling
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=m2vdpr2wv4.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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.