Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH V6 1/3] gdb: support for eBPF
Date: Mon, 03 Aug 2020 17:52:15 +0200	[thread overview]
Message-ID: <87o8nrengw.fsf@oracle.com> (raw)
In-Reply-To: <SN6PR11MB28934767080FF05DFE61C17FC44D0@SN6PR11MB2893.namprd11.prod.outlook.com> (Tankut Baris Aktemur's message of "Mon, 3 Aug 2020 14:55:43 +0000")


Hello.

> On Monday, August 3, 2020 4:03 PM, Jose E. Marchesi wrote:
>> This patch adds basic support for the eBPF target: tdep and build
>> machinery.  The accompanying simulator is introduced in subsequent
>> patches.
>>
>> +/* Internal debugging facilities.  */
>> +
>> +/* When this is set to non-zero debugging information will be
>> +   printed.  */
>> +
>> +static unsigned int bpf_debug_flag = 0;
>> +
>> +/* The show callback for 'show debug bpf'.  */
>> +
>> +static void
>> +show_bpf_debug (struct ui_file *file, int from_tty,
>> +	        struct cmd_list_element *c, const char *value)
>
> Just my two cents.  The 'struct' keyword can be removed in numerous places
> throughout the file.  Also, NULL can be replaced with nullptr.

I prefer to write (and maintain) C.

>> +{
>> +  fprintf_filtered (file, _("Debugging of BPF is %s.\n"), value);
>> +}
>> +
>> +
>> 
>> 
>> +/* BPF registers */
>
> Might look better with dot-space-space at the end.

Yeah, will add the missing dot-spacing in this and other instances you
identified.

Thanks for the feedback! :)


  reply	other threads:[~2020-08-03 15:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 14:02 [PATCH V6 0/3] eBPF support Jose E. Marchesi
2020-08-03 14:02 ` [PATCH V6 1/3] gdb: support for eBPF Jose E. Marchesi
2020-08-03 14:52   ` Eli Zaretskii
2020-08-03 15:04     ` Jose E. Marchesi
2020-08-03 14:55   ` Aktemur, Tankut Baris
2020-08-03 15:52     ` Jose E. Marchesi [this message]
2020-08-03 16:00       ` Simon Marchi
2020-08-03 16:46         ` Jose E. Marchesi
2020-08-04 13:41       ` Andrew Burgess
2020-08-04 14:57         ` Jose E. Marchesi
2020-08-04 16:29           ` Simon Marchi
2020-08-05  9:21           ` Andrew Burgess
2020-08-05 13:00             ` Simon Marchi
2020-08-03 14:02 ` [PATCH V6 2/3] sim: eBPF simulator Jose E. Marchesi
2020-08-04 14:50   ` Andrew Burgess
2020-08-04 15:32     ` Jose E. Marchesi
2020-08-03 14:02 ` [PATCH V6 3/3] sim: generated files for the " Jose E. Marchesi
2020-08-04 13:51   ` Andrew Burgess
2020-08-04 14:59     ` Jose E. Marchesi

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=87o8nrengw.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tankut.baris.aktemur@intel.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