Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Kamil Rytarowski <kamil@netbsd.org>,
	Andrew Burgess <andrew.burgess@embecosm.com>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 04/10] Add netbsd_nat::pid_to_exec_file
Date: Mon, 7 Sep 2020 14:48:40 -0400	[thread overview]
Message-ID: <7f8fb7bd-f0d4-2ab0-1bfd-d8d624c78c0f@simark.ca> (raw)
In-Reply-To: <3562912c-2b32-2b5a-308a-d4a28d12f5d9@netbsd.org>

On 2020-09-07 9:36 a.m., Kamil Rytarowski wrote:
>> The convention in GDB is to document global functions in the header
>> file, and leave a comment '/* See xxxx.h.  */' in the source file.
>>
>> Thanks,
>> Andrew
>>
>>
> OK. I will do it in v3.
> 

Thanks, don't forget to apply it in other other patches too (such as 05/10).

Simon


  reply	other threads:[~2020-09-07 18:48 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04  0:28 [PATCH v2 00/10] Add minimal NetBSD/amd64 gdbserver support Kamil Rytarowski
2020-09-04  0:28 ` [PATCH v2 01/10] Add handle_eintr to wrap EINTR handling in syscalls Kamil Rytarowski
2020-09-07 14:06   ` Simon Marchi
2020-09-07 14:59     ` Kamil Rytarowski
2020-10-12 17:56       ` [PATCH] gdb::handle_eintr, remove need to specify return type (Re: [PATCH v2 01/10] Add handle_eintr to wrap EINTR handling in syscalls) Pedro Alves
2020-10-13 13:43         ` Kamil Rytarowski
2020-10-13 14:17           ` [PATCH v2] gdb::handle_eintr, remove need to specify return type Pedro Alves
2020-10-13 14:54             ` Kamil Rytarowski
2020-10-16 20:51             ` Tom Tromey
2020-10-26 14:00               ` Pedro Alves
2020-10-26 14:20                 ` Tom Tromey
2020-10-26 18:59                   ` Pedro Alves
2020-09-04  0:28 ` [PATCH v2 02/10] Register a placeholder for NetBSD shared functions in gdb/nat Kamil Rytarowski
2020-09-07 18:44   ` Simon Marchi
2020-09-07 19:49     ` Kamil Rytarowski
2020-09-04  0:28 ` [PATCH v2 03/10] Build nat/netbsd-nat.o for the NetBSD native target Kamil Rytarowski
2020-09-04  0:28 ` [PATCH v2 04/10] Add netbsd_nat::pid_to_exec_file Kamil Rytarowski
2020-09-07  7:57   ` Andrew Burgess
2020-09-07 13:36     ` Kamil Rytarowski
2020-09-07 18:48       ` Simon Marchi [this message]
2020-09-07 18:47   ` Simon Marchi
2020-09-07 19:51     ` Kamil Rytarowski
2020-09-04  0:29 ` [PATCH v2 05/10] Add gdb/nat common functions for listing threads Kamil Rytarowski
2020-09-07 18:59   ` Simon Marchi
2020-09-07 19:57     ` Kamil Rytarowski
2020-09-04  0:29 ` [PATCH v2 06/10] Add netbsd_nat::enable_proc_events in gdb/nat Kamil Rytarowski
2020-09-04  0:29 ` [PATCH v2 07/10] Add a common utility function to read and write siginfo_t in inferior Kamil Rytarowski
2020-09-04  0:29 ` [PATCH v2 08/10] Avoid double free in startup_inferior Kamil Rytarowski
2020-09-07 19:19   ` Simon Marchi
2020-09-08  0:54     ` Kamil Rytarowski
2020-09-08  2:21       ` Simon Marchi
2020-09-04  0:29 ` [PATCH v2 09/10] Switch local native code to gdb/nat shared functions Kamil Rytarowski
2020-09-07 19:24   ` Simon Marchi
2020-09-08  0:04     ` Kamil Rytarowski
2020-09-04  0:29 ` [PATCH v2 10/10] Add minimal and functional NetBSD/amd64 gdbserver Kamil Rytarowski
2020-09-07 19:58   ` Simon Marchi
2020-09-08  0:03     ` Kamil Rytarowski

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=7f8fb7bd-f0d4-2ab0-1bfd-d8d624c78c0f@simark.ca \
    --to=simark@simark.ca \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kamil@netbsd.org \
    --cc=tom@tromey.com \
    /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