Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Reset errno before PTRACE_PEEKUSER for MIPS DSP_CONTROL
Date: Wed, 03 Sep 2014 21:21:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1409031517450.27075@tp.orcam.me.uk> (raw)
In-Reply-To: <20140903125111.GF12084@jhogan-linux.le.imgtec.org>

On Wed, 3 Sep 2014, James Hogan wrote:

> > > gdb/:
> > > 	* mips-linux-nat.c (mips_linux_read_description): Reset errno to 0
> > > 	prior to reading DSP_CONTROL with PTRACE_PEEKUSER ptrace call.
> > > 
> > > gdb/gdbserver/:
> > > 	* linux-mips-low.c (mips_read_description): Reset errno to 0 prior
> > > 	to reading DSP_CONTROL with PTRACE_PEEKUSER ptrace call.
> > 
> >  This is fine, go ahead and apply it.  Thanks.
> 
> Thanks for reviewing it Maciej.
> 
> This is my first GDB patch submitted upstream (although I have a pile of
> RFC patches for FR=1, FRE=1, MSA support I'm still getting into shape),
> so I don't have push access yet. Is it easy to arrange?

 Sure, that can be arranged, but you need to prove yourself by submitting 
a few more good patches first though.  And assuming you've got a copyright 
assignment in place with FSF, either personally or on behalf of your 
employer (I presume you do, but please confirm as you start sending larger 
changes).  You'll have to speak with one of the general maintainers when 
the right time comes.

 I have applied your change now, thanks.

 BTW, I've had some FR=1 stuff ongoing too, though regrettably stalled 
recently, see:

https://sourceware.org/bugzilla/show_bug.cgi?id=7518
http://sourceware.org/ml/gdb-patches/2012-06/msg00201.html

-- based on an old patch from MIPS Technologies that wasn't quite there, 
but still was a good starting point.  Bare iron only of course as there 
was no FR=1 Linux ABI up until recently.  It will be interesting to see 
how the two pieces compare.  Or actually it may make sense if I push my 
piece first, there was just some concern about regcache that remained
unresolved, so I'll see if I can reintegrate that change against current
trunk, retest and repost.

  Maciej


  reply	other threads:[~2014-09-03 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 21:48 James Hogan
2014-09-03 12:41 ` Maciej W. Rozycki
2014-09-03 12:51   ` James Hogan
2014-09-03 21:21     ` Maciej W. Rozycki [this message]
2014-09-17 16:22       ` Sergio Durigan Junior

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.DEB.1.10.1409031517450.27075@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=james.hogan@imgtec.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