From: John Baldwin <jhb@freebsd.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 5/5] Document support for 'info proc' on FreeBSD.
Date: Thu, 04 Jan 2018 21:36:00 -0000 [thread overview]
Message-ID: <3780342.xYbeyQhyDV@ralph.baldwin.cx> (raw)
In-Reply-To: <83efn5bmuq.fsf@gnu.org>
On Thursday, January 04, 2018 06:38:37 PM Eli Zaretskii wrote:
> > From: John Baldwin <jhb@FreeBSD.org>
> > Date: Wed, 3 Jan 2018 17:49:23 -0800
> >
> > Since the 'info proc' support on FreeBSD does not use /proc, reword
> > the documentation for 'info proc' to not assume /proc. This includes
> > renaming the node to 'Process Information' and suggesting that
> > additional process information can be queried via different
> > OS-specific interfaces. This is also cleans up the description of
> > 'info proc' support for core files a bit as /proc is not used for core
> > file support on any current platform.
> >
> > gdb/doc/ChangeLog:
> >
> > * gdb.texinfo (pwd): Update cross-reference for Process Information
> > node and remove explicit /proc reference.
> > (Native): Rename subsection from SVR4 Process Information to
> > Process Information.
> > (Process Information): Reword introduction to be less /proc
> > centric. Document support for "info proc" on FreeBSD.
>
> OK, thanks.
>
> Do we need a NEWS entry for this?
I suppose so. I added this to the documentation patch locally:
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 5812e8f357..ac2bf57401 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2018-01-04 John Baldwin <jhb@FreeBSD.org>
+
+ * NEWS: Document that 'info proc' now works on FreeBSD.
+
2018-01-03 John Baldwin <jhb@FreeBSD.org>
* configure.ac: Check for kinfo_getfile in libutil.
diff --git a/gdb/NEWS b/gdb/NEWS
index 14fcdf8674..7b415ce6e6 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -3,6 +3,9 @@
*** Changes since GDB 8.0
+* 'info proc' now works on running processes on FreeBSD systems and core
+ files created on FreeBSD systems.
+
* GDB now supports dynamically creating arbitrary register groups specified
in XML target descriptions. This allows for finer grain grouping of
registers on systems with a large amount of registers.
--
John Baldwin
next prev parent reply other threads:[~2018-01-04 21:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 1:50 [PATCH v2 0/5] Support for 'info proc' on FreeBSD cores and native John Baldwin
2018-01-04 1:50 ` [PATCH v2 3/5] Use gdb::unique_xmalloc_ptr<> instead of a deleter that invokes free() John Baldwin
2018-01-05 2:58 ` Simon Marchi
2018-01-04 1:50 ` [PATCH v2 1/5] Support 'info proc' for FreeBSD process core dumps John Baldwin
2018-01-05 2:54 ` Simon Marchi
2018-01-05 19:43 ` John Baldwin
2018-01-09 19:29 ` Simon Marchi
2018-01-04 1:50 ` [PATCH v2 2/5] Don't return stale data from fbsd_pid_to_exec_file for kernel processes John Baldwin
2018-01-05 2:57 ` Simon Marchi
2018-01-05 19:43 ` John Baldwin
2018-01-04 1:59 ` [PATCH v2 5/5] Document support for 'info proc' on FreeBSD John Baldwin
2018-01-04 16:38 ` Eli Zaretskii
2018-01-04 21:36 ` John Baldwin [this message]
2018-01-05 6:53 ` Eli Zaretskii
2018-01-04 1:59 ` [PATCH v2 4/5] Support 'info proc' for native FreeBSD processes John Baldwin
2018-01-05 3:20 ` Simon Marchi
2018-01-05 19:43 ` 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=3780342.xYbeyQhyDV@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=eliz@gnu.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).