[Bug 250024] cannot set CPU register value

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=250024


John Reiser <jreiser at bitwagon.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
         Resolution|                            |CURRENTRELEASE




--- Comment #8 from John Reiser <jreiser at bitwagon.com>  2008-08-11 13:52:10 EDT ---
gdb-6.8-17.fc9 also works for me.  So -17 and -12 work, but -5 still had the
problem.  I hope it continues to work.  I changed Status to Closed - Current
Release.

This looks to be strongly related to bug #436037, "gdb remote fails qemu: Value
being assigned to is no longer active".  One theme seems to be keeping hardware
registers fully active regardless of the status of other pieces of the
environment, such as symbol tables, stack traces, etc.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.