Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: <binutils@sourceware.org>,  <gdb-patches@sourceware.org>,
	 Pedro Alves <palves@redhat.com>,
	 Djordje Todorovic <djordje.todorovic@rt-rk.com>
Subject: Re: [PATCH 0/4] Fix issues with Linux core PRPSINFO note definitions
Date: Sat, 23 Sep 2017 02:10:00 -0000	[thread overview]
Message-ID: <874lruxj0r.fsf@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1709220216120.16752@tp.orcam.me.uk> (Maciej	W. Rozycki's message of "Sat, 23 Sep 2017 01:02:20 +0100")

On Friday, September 22 2017, Maciej W. Rozycki wrote:

> Hi,
>
>  This patch series addresses problems with Linux core PRPSINFO note 
> definitions, discovered in the course of Djordje's MIPS PID extraction 
> patch review.  See individual patch descriptions for details.
>
>  These changes have passed binutils regression testing against my usual 
> targets (for the BFD part) and also native GDB regression testing with the 
> `x86_64-linux-gnu' target and the `mips-linux-gnu' n64 target (for the GDB 
> part, and the `gcore' command in particular).
>
>  OK to apply?

Hey Maciej,

Aside from a small nit on patch #3, I really like the direction you
chose on this patch.  I am not a binutils maintainer and not a GDB
global maintainer, so I cannot approve it, but it does look good to me
and makes the existing code more logical and simpler to follow.

I also like the fact that you removed the responsibility that GDB had to
decide which prpsinfo structure it would use.  That's something I
remember struggling with when I was hacking the initial patch, and I'm
glad this patch solves it.

So, LGTM.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  parent reply	other threads:[~2017-09-23  2:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-23  0:02 Maciej W. Rozycki
2017-09-23  0:03 ` [PATCH 1/4] ELF/BFD: Fix padding in `elf_external_linux_prpsinfo64' Maciej W. Rozycki
2017-09-23  0:04 ` [PATCH 2/4] ELF/BFD,GDB: Handle both variants of the 32-bit Linux core PRPSINFO note Maciej W. Rozycki
2017-09-23  0:04 ` [PATCH 3/4] ELF/BFD: Handle both variants of the 64-bit " Maciej W. Rozycki
2017-09-23  2:05   ` Sergio Durigan Junior
2017-09-24 22:19     ` Maciej W. Rozycki
2017-09-24 23:32       ` Sergio Durigan Junior
2017-09-25  9:48         ` Maciej W. Rozycki
2017-09-25 16:49           ` Sergio Durigan Junior
2017-09-23  0:05 ` [PATCH 4/4] GDB: Remove Linux core PRPSINFO note writer override Maciej W. Rozycki
2017-09-23  2:10 ` Sergio Durigan Junior [this message]
2017-09-24 23:46 ` [PATCH 0/4] Fix issues with Linux core PRPSINFO note definitions Alan Modra
2017-09-29 21:11 ` [PING][PATCH " Maciej W. Rozycki
2017-10-11  0:32   ` [PING^2][PATCH " Maciej W. Rozycki
2017-10-11  9:41     ` Pedro Alves
2017-10-11 14:06       ` Maciej W. Rozycki

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=874lruxj0r.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=djordje.todorovic@rt-rk.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@imgtec.com \
    --cc=palves@redhat.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