Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/6] Add support for 'info proc files' on FreeBSD core dumps.
Date: Mon, 17 Sep 2018 16:54:00 -0000	[thread overview]
Message-ID: <0f1f7314-5760-6ae1-1a25-b9d42ff8ffb8@FreeBSD.org> (raw)
In-Reply-To: <eacbb74e-2f6c-441a-90b2-ddbbe6dbc03a@simark.ca>

On 9/15/18 7:27 PM, Simon Marchi wrote:
> Some nits about the comments, otherwise LGTM (I didn't check the
> bits-reading code in detail, I assumed it wash largely unchanged).

Yes, the bits-reading code hasn't changed.
 
> On 2018-09-12 7:37 p.m., John Baldwin wrote:
>> +
>> +/* Output the header for "info proc files".  */
> 
> This should be /* See fbsd-tdep.h.  */, same for fbsd_info_proc_files_entry.

Ok, fixed both locally.

>> +void
>> +fbsd_info_proc_files_header ()
>> +{
>> +  printf_filtered (_("Open files:\n\n"));
>> +  printf_filtered ("  %6s %6s %10s %9s %s\n",
>> +		   "FD", "Type", "Offset", "Flags  ", "Name");
>> +}
> 
> ...
> 
>> +/* Output description of a single file descriptor for "info proc
>> +   files".  The KF_TYPE, KF_FD, KF_FLAGS, KF_OFFSET, KF_VNODE_TYPE,
>> +   KF_SOCK_DOMAIN, KF_SOCK_TYPE, and KF_SOCK_PROTOCOL parameters
>> +   should contain the value of the corresponding fields in a 'struct
>> +   kinfo_file'.  The KF_SA_LOCAL, KF_SA_PEER, and KF_PATH parameters
>> +   should contain pointers to the corresponding fields in a 'struct
>> +   kinfo_file'. */
> 
> Some parameters name in the doc here don't match the actual names below.
> 
>> +extern void fbsd_info_proc_files_entry (int kf_type, int kf_fd, int kf_flags,
>> +					LONGEST kf_offset, int kf_vnode_type,
>> +					int kf_sock_domain, int kf_sock_type,
>> +					int kf_sock_protocol,
>> +					const void *kf_sa_local,
>> +					const void *fa_sa_peer,
>> +					const void *path);

Huh, I'm not sure how I botched that, but I've fixed.  The comment was
correct, and the actual function definition matched the comment.  Only the
prototype was wrong.
-- 
John Baldwin

                                                                            


  reply	other threads:[~2018-09-17 16:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 23:37 [PATCH v2 0/6] Add a new 'info proc files' command John Baldwin
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 2/6] Add a new 'info proc files' subcommand of 'info proc' 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 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 [this message]
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: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=0f1f7314-5760-6ae1-1a25-b9d42ff8ffb8@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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