public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/6] Add a new 'info proc files' command
Date: Wed, 12 Sep 2018 23:37:00 -0000	[thread overview]
Message-ID: <20180912233707.43492-1-jhb@FreeBSD.org> (raw)

This should include most of the suggested documentation fixes from the
first series.  It also adds an additional patch that attempts to tidy up
some of the other "info proc" documentation.  One change I haven't made
(wasn't sure if it was still desired) was if we wanted to replace the
specific annotations on individual 'info proc' subcommands about which
OS's supported those commands with a single, more general statement that
commands may only be supported on a subset of systems supported by GDB.

I've moved more of the shared code for generating the 'info proc files'
output to fbsd-tdep.c.

One open question still from the first series is if GDB can assume the
presence of routines like 'inet_ntoa' and 'inet_ntop' for formatting
IPv4 and IPv6 addresses.  It seems GDB does assume the presence of
newer routines (e.g. getaddrinfo()) on POSIX systems in other places
(e.g. ser-tcp.c), though in those places we use different APIs for
Win32.

John Baldwin (6):
  Use KF_PATH to verify the size of a struct kinfo_file.
  Add a new 'info proc files' subcommand of 'info proc'.
  Add support for 'info proc files' on FreeBSD core dumps.
  Support 'info proc files' on live FreeBSD processes.
  Document the 'info proc files' command.
  Make the "info proc" documentation more consistent.

 gdb/ChangeLog       |  58 ++++++
 gdb/NEWS            |   3 +
 gdb/defs.h          |   3 +
 gdb/doc/ChangeLog   |  10 +
 gdb/doc/gdb.texinfo |  34 +++-
 gdb/fbsd-nat.c      |  32 ++-
 gdb/fbsd-tdep.c     | 468 +++++++++++++++++++++++++++++++++++++++++++-
 gdb/fbsd-tdep.h     |  20 ++
 gdb/infcmd.c        |  24 ++-
 9 files changed, 638 insertions(+), 14 deletions(-)

-- 
2.18.0

             reply	other threads:[~2018-09-12 23:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 23:37 John Baldwin [this message]
2018-09-12 23:37 ` [PATCH v2 3/6] Add support for 'info proc files' on FreeBSD core dumps John Baldwin
2018-09-16  2:27   ` Simon Marchi
2018-09-17 16:54     ` John Baldwin
2018-09-12 23:37 ` [PATCH v2 5/6] Document the 'info proc files' command John Baldwin
2018-09-13 13:39   ` Eli Zaretskii
2018-09-12 23:37 ` [PATCH v2 1/6] Use KF_PATH to verify the size of a struct kinfo_file John Baldwin
2018-09-12 23:37 ` [PATCH v2 6/6] Make the "info proc" documentation more consistent John Baldwin
2018-09-13 13:40   ` Eli Zaretskii
2018-09-12 23:37 ` [PATCH v2 2/6] Add a new 'info proc files' subcommand of 'info proc' John Baldwin
2018-09-12 23:43 ` [PATCH v2 4/6] Support 'info proc files' on live FreeBSD processes John Baldwin
2018-09-16  2:34 ` [PATCH v2 0/6] Add a new 'info proc files' command Simon Marchi
2018-09-17 16:59   ` John Baldwin
2018-09-17 17:17     ` Simon Marchi

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=20180912233707.43492-1-jhb@FreeBSD.org \
    --to=jhb@freebsd.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).