Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Simon Ser <contact@emersion.fr>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v5] Generate NT_PROCSTAT_{AUXV,VMMAP,PS_STRINGS} in FreeBSD coredumps
Date: Thu, 06 Sep 2018 22:12:00 -0000	[thread overview]
Message-ID: <5430f3af-598e-fd53-ca30-e21b4eb0b643@FreeBSD.org> (raw)
In-Reply-To: <6iz9XpK7m-0Fumt1t9LmZGLgi6vpQ8dIh21if-zu7fbvUH51Ef4YYAjZHt80Cy2YmoviGYM9Igaebc8024iHdtxKDGBNQOJpKhKrFD5lnjw=@emersion.fr>

On 9/2/18 1:01 PM, Simon Ser wrote:
> Hi John,
> 
> Did you have time to have a look at this new version ?

Yes, sorry for the delay.  I've fixed a few small nits (updating gdb/ChangeLog,
adding a reference to a PR that this change fixes by including auxv info in
gcore output, etc.) and pushed it.
-- 
John Baldwin

                                                                            


      reply	other threads:[~2018-09-06 22:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 12:35 [PATCH] Generate NT_PROCSTAT_{AUXV,VMMAP} " Simon Ser
2018-07-11 16:16 ` John Baldwin
2018-07-11 16:40   ` Simon Ser
2018-07-16 13:39 ` [PATCH v2] Generate NT_PROCSTAT_{AUXV,VMMAP,PS_STRINGS} " Simon Ser
2018-07-24  7:53   ` Simon Ser
2018-08-01 16:33     ` Simon Ser
2018-08-01 18:16   ` John Baldwin
2018-08-21 14:45   ` [PATCH v3] " Simon Ser
2018-08-23 10:40     ` John Baldwin
2018-08-23 14:02     ` [PATCH v4] " Simon Ser
2018-08-23 16:16       ` John Baldwin
2018-08-23 17:11       ` [PATCH v5] " Simon Ser
2018-09-02 20:02         ` Simon Ser
2018-09-06 22:12           ` John Baldwin [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=5430f3af-598e-fd53-ca30-e21b4eb0b643@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=contact@emersion.fr \
    --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