public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH v2 1/6] Add support to readelf for reading FreeBSD ELF core notes.
Date: Thu, 14 Jan 2016 05:30:00 -0000	[thread overview]
Message-ID: <20160114052823.GH1270@bubble.grove.modra.org> (raw)
In-Reply-To: <1452721551-657-2-git-send-email-jhb@FreeBSD.org>

On Wed, Jan 13, 2016 at 01:45:46PM -0800, John Baldwin wrote:
> binutils/ChangeLog:
> 
> 	* readelf.c (get_freebsd_elfcore_note_type): New
> 	(process_note): Add support for FreeBSD core notes.
> 
> include/elf/ChangeLog:
> 
> 	* common.h (NT_FREEBSD_THRMISC): Define.
> 	(NT_FREEBSD_PROCSTAT_PROC): Define.
> 	(NT_FREEBSD_PROCSTAT_FILES): Define.
> 	(NT_FREEBSD_PROCSTAT_VMMAP): Define.
> 	(NT_FREEBSD_PROCSTAT_GROUPS): Define.
> 	(NT_FREEBSD_PROCSTAT_UMASK): Define.
> 	(NT_FREEBSD_PROCSTAT_RLIMIT): Define.
> 	(NT_FREEBSD_PROCSTAT_OSREL): Define.
> 	(NT_FREEBSD_PROCSTAT_PSSTRINGS): Define.
> 	(NT_FREEBSD_PROCSTAT_AUXV): Define.

OK, but I deleted include/elf/ChangeLog deliberately, so the entry goes in
include/ChangeLog and looks like

	* elf/common.h (NT_FREEBSD_THRMISC): Define.
	...

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2016-01-14  5:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 21:46 [PATCH v2 0/6] Support kernel-backed user threads on FreeBSD John Baldwin
2016-01-13 21:46 ` [PATCH v2 1/6] Add support to readelf for reading FreeBSD ELF core notes John Baldwin
2016-01-14  5:30   ` Alan Modra [this message]
2016-01-14  5:40     ` John Baldwin
2016-01-13 21:46 ` [PATCH v2 2/6] Add a psuedosection for the NT_FREEBSD_THRMISC note John Baldwin
2016-01-14  5:30   ` Alan Modra
2016-01-13 21:46 ` [PATCH v2 6/6] Dump register notes for each thread when generating a FreeBSD core John Baldwin
2016-01-14 15:34   ` Pedro Alves
2016-01-13 21:46 ` [PATCH v2 3/6] Display per-thread information for threads in FreeBSD cores John Baldwin
2016-01-14 15:03   ` Pedro Alves
2016-01-15 20:23     ` John Baldwin
2016-01-18 12:27       ` Pedro Alves
2016-01-18 17:06         ` John Baldwin
2016-01-18 17:13           ` Pedro Alves
2016-01-13 21:52 ` [PATCH v2 5/6] Add support for LWP-based threads on FreeBSD John Baldwin
2016-01-14 15:29   ` Pedro Alves
2016-01-15 23:54     ` John Baldwin
2016-01-16 14:47       ` Pedro Alves
2016-01-13 21:52 ` [PATCH v2 4/6] Use LWP IDs with ptrace register requests " John Baldwin
2016-01-14 15:07   ` Pedro Alves
2016-01-15 20:23     ` John Baldwin
2016-01-15 21:41       ` Pedro Alves
2016-01-15 23:54         ` John Baldwin
2016-01-16 14:39           ` Pedro Alves
2016-01-16 19:17             ` John Baldwin

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=20160114052823.GH1270@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.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).