public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Convert have_ptrace_getregset to a tri-state boolean
Date: Tue, 23 Jun 2015 13:05:00 -0000	[thread overview]
Message-ID: <558959A4.6050003@gmail.com> (raw)
In-Reply-To: <1434551008-1013-1-git-send-email-yao.qi@linaro.org>

On 17/06/15 15:23, Yao Qi wrote:
> gdb:
>
> 2015-06-17  Yao Qi<yao.qi@linaro.org>
>
> 	* amd64-linux-nat.c (amd64_linux_fetch_inferior_registers):
> 	Check whether have_ptrace_getregset is TRIBOOL_TRUE explicitly.
> 	(amd64_linux_store_inferior_registers): Likewise.
> 	* arm-linux-nat.c (fetch_fpregister): Likewise.
> 	(fetch_fpregs, store_fpregister): Likewise.
> 	(store_fpregister, store_fpregs): Likewise.
> 	(fetch_register, fetch_regs): Likewise.
> 	(store_register, store_regs): Likewise.
> 	(fetch_vfp_regs, store_vfp_regs): Likewise.
> 	(arm_linux_read_description): Check have_ptrace_getregset is
> 	TRIBOOL_UNKNOWN.  Set have_ptrace_getregset to TRIBOOL_TRUE
> 	or TRIBOOL_FALSE.
> 	* i386-linux-nat.c (fetch_xstateregs): Check
> 	have_ptrace_getregset is not TRIBOOL_TRUE.
> 	(store_xstateregs): Likewise.
> 	* linux-nat.c (have_ptrace_getregset): Change its type to
> 	enum tribool.
> 	* linux-nat.h (tribool): New enum.
> 	* x86-linux-nat.c (x86_linux_read_description): Use enum tribool.
> 	Check whether have_ptrace_getregset is TRIBOOL_TRUE.

I've pushed it in.

-- 
Yao (齐尧)

      reply	other threads:[~2015-06-23 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 14:23 Yao Qi
2015-06-23 13:05 ` Yao Qi [this message]

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=558959A4.6050003@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).