Hi,

ppc-linux-nat.c:store_vsx_register fetches the VSX registers into a
buffer, changes the value of the relevant register and then stores the
buffer again with ptrace.

The problem is, the function was "fetching" the VSX registers using
PTRACE_SETVSXREGS instead of PTRACE_GETVSXREGS. Ouch.

This patch fixes the typo, and also fixes the vsx-regs.exp testcase to
use gdb_test instead of send_gdb (this also fixes some synchronization
issues in the test), and updates the expect info reg output with the new
v2_double member.

gdbserver doesn't have this bug, the vsx-regs.exp test passes there
(except for the core file tests which are unsupported in gdbserver).

There are no regressions in the testsuite. Ok to commit? Ok for the
branch too?

-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


2010-07-20  Thiago Jung Bauermann  <bauerman@br.ibm.com>

gdb/
	* ppc-linux-nat.c (store_vsx_register): Use PTRACE_GETVSXREGS to get
	VSX registers contents.

gdb/testsuite/
	* gdb.arch/vsx-regs.exp: Remove wrong comment about testing AltiVec
	registers.  Update data sets with the new v2_double element in the VSX
	register union.  Add vector_register3_vr data set for the AltiVec
	registers.  Use gdb_test instead of send_gdb.