Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@wdc.com>
To: Jim Wilson <jimw@sifive.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	    Andrew Burgess <andrew.burgess@embecosm.com>,
	    Palmer Dabbelt <palmer@dabbelt.com>,
	Tom Tromey <tom@tromey.com>,
	    "guoren@kernel.org" <guoren@kernel.org>,
	    "lifang_xia@c-sky.com" <lifang_xia@c-sky.com>,
	    "yunhai_shang@c-sky.com" <yunhai_shang@c-sky.com>,
	    "jiangshuai_li@c-sky.com" <jiangshuai_li@c-sky.com>
Subject: Re: [PATCH v2 3/3] gdbserver: Add RISC-V/Linux support
Date: Thu, 30 Jan 2020 01:58:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.21.2001300006200.14118@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <CAFyWVaapE78div4jp65HrHLyRogbkWyg-XYeLxXUa-3f8MZE-Q@mail.gmail.com>

On Wed, 29 Jan 2020, Jim Wilson wrote:

> I noticed on the gdbserver console I'm getting a lot of ptrace warnings.
>     ptrace(regsets_fetch_inferior_registers) PID=1678103: Invalid argument
>     Warning: ptrace(regsets_store_inferior_registers): Invalid argument
> This looks like a side effect of having two FP regsets defined, it
> tries the first one, fails, and then tries the second one which is
> correct.  If you mark them as OPTIONAL_REGS we would only get the
> warning once which would be OK, except that they can't be both FP_REGS
> and OPTIONAL_REGS at the same time.  I don't know what if anything
> would break if they aren't marked as FP_REGS.   I only see explicit
> checks for GENERAL_REGS and OPTIONAL_REGS; I don't see any checks for
> FP_REGS.  Anyways, I would suggest as a future improvement that the
> linux gdbserver regset support be extended so that a regset can be
> marked as both FP_REGS and OPTIONAL_REGS.

 Hmm, good point.  I think OPTIONAL_REGS might become a flag, however as 
you have observed there seems to be no special meaning indeed to FP_REGS 
and actually only a couple of `gdbserver' hosts use this type, so using 
OPTIONAL_REGS should be fine.  I'll send an update.

> There are some new functions and structures that don't have
> explanatory comments before them, but this is a minor issue.

 Right, though I think they are self-explanatory.

  Maciej


      reply	other threads:[~2020-01-30  0:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.21.2001291207310.14118@redsun52.ssa.fujisawa.hgst.com>
2020-01-29 18:13 ` [PATCH v2 1/3] RISC-V/Linux/native: Determine FLEN dynamically Maciej W. Rozycki
2020-01-29 23:26   ` Jim Wilson
2020-01-30  0:13     ` Maciej W. Rozycki
2020-01-30 23:19   ` Jim Wilson
2020-01-31  0:06     ` Andreas Schwab
2020-01-31 12:11     ` Maciej W. Rozycki
2020-01-29 18:14 ` [PATCH v2 2/3] RISC-V/Linux/native: Factor out target description determination Maciej W. Rozycki
2020-01-29 23:39   ` Jim Wilson
     [not found] ` <alpine.LFD.2.21.2001291412560.14118@redsun52.ssa.fujisawa.hgst.com>
2020-01-30  0:00   ` [PATCH v2 3/3] gdbserver: Add RISC-V/Linux support Jim Wilson
2020-01-30  1:58     ` Maciej W. Rozycki [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=alpine.LFD.2.21.2001300006200.14118@redsun52.ssa.fujisawa.hgst.com \
    --to=macro@wdc.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guoren@kernel.org \
    --cc=jiangshuai_li@c-sky.com \
    --cc=jimw@sifive.com \
    --cc=lifang_xia@c-sky.com \
    --cc=palmer@dabbelt.com \
    --cc=tom@tromey.com \
    --cc=yunhai_shang@c-sky.com \
    /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