This is the mail archive of the gdb-patches@sourceware.org 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: RFC: partially available registers

From: Tom Tromey <tromey at redhat dot com>
To: Pedro Alves <pedro at codesourcery dot com>
Cc: gdb-patches at sourceware dot org, "H.J. Lu" <hjl dot tools at gmail dot com>, Daniel Jacobowitz <drow at false dot org>
Date: Tue, 26 Jul 2011 13:19:47 -0600
Subject: Re: RFC: partially available registers
References: <m3vcv6xegp.fsf@fleche.redhat.com> <m3mxg6w1si.fsf@fleche.redhat.com> <201107261631.18672.pedro@codesourcery.com> <201107261707.37547.pedro@codesourcery.com>

>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

Pedro> I glanced at:
Pedro>  <http://kerneltrap.org/mailarchive/linux-kernel/2010/2/10/4537101/thread>

Pedro> and now I'm not sure my last assumption with ptrace stopped tasks
Pedro> holds.  If not, then we have two distinct cases to handle -- x87 state
Pedro> has never been accessed; and x87 state in the xsave memory area is
Pedro> not up to date.  Is that true?  Is there a way to distinguish them?
Pedro> Is that what linux puts in the SW usable bytes [464..511]?

I do not know.  I think it would be best if H.J. weighed in on this.

Tom

References:
- RFC: partially available registers
  - From: Tom Tromey
- Re: RFC: partially available registers
  - From: Tom Tromey
- Re: RFC: partially available registers
  - From: Pedro Alves
- Re: RFC: partially available registers
  - From: Pedro Alves

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