This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Set ADDR

From: Elena Zannoni <ezannoni at redhat dot com>
To: Andrew Cagney <ac131313 at ges dot redhat dot com>
Cc: gdb-patches at sources dot redhat dot com
Date: Wed, 21 Aug 2002 20:59:15 -0400
Subject: Re: Set ADDR
References: <3D630A21.5060308@ges.redhat.com><3D63B550.4010807@ges.redhat.com>

Andrew Cagney writes:
 > PS: If anyone things this is just a PPC bug:
 > 
 > (top-gdb) info registers
 > eax            0xbffff864       -1073743772
 > ecx            0x0      0
 > ...
 > (top-gdb) set $ecx = 0
 > (top-gdb) info registers
 > eax            0x0      0
 > ecx            0x0      0
 > ...
 > 
 > So I guess two things:
 > 
 > - GDB's testsuite doesn't cover this

The altivec-regs.exp file covers this, and, soon, a booke-regs.exp.
But nothing else.

 > - Someone modifying a register or register variable is a pretty rare 
 > occurance
 > 

Yeah. I noticed this failure last night while retesting the booke code,
but by morning it was fixed! Miracle!

 > Perhaphs I should add a sleep(1) to the value write code and see how 
 > long it takes someone to notice that ;-)
 > 
 > enjoy,
 > Andrew

References:
- Set ADDR
  - From: Andrew Cagney
- Re: Set ADDR
  - From: Andrew Cagney

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]