From: Simon Marchi <simark@simark.ca>
To: "Battig, Caleb" <Caleb.Battig@netapp.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "Lovett, Stuart" <Stuart.Lovett@netapp.com>,
"Peikes, Wendy" <Wendy.Peikes@netapp.com>
Subject: Re: [PING][PING] Added x86_64 stub for debugging embedded systems running on Intel x86_64 processor architecture.
Date: Tue, 20 Oct 2020 09:09:26 -0400 [thread overview]
Message-ID: <074c171f-c4c0-d50f-0b51-c2d3e7e79ad3@simark.ca> (raw)
In-Reply-To: <BL0PR06MB441875F02C5734A25BCD6F48E11E0@BL0PR06MB4418.namprd06.prod.outlook.com>
On 2020-10-19 6:23 p.m., Battig, Caleb wrote:
> Simon,
>
> Thanks so much for looking into this. This is a significant addition to GDB that has the potential to help a lot of developers.
>
> I've made some formatting changes. See the attached patch. I'm not sure what you meant by your comment on whitespace and indentation, but I made all the other changes.
>
> Thanks,
For example, if a line is indented by 18 columns, that means you'll have
two tabs (worth 16 columns) followed by two spaces (for a total of 18
columns).
You can find the faulty lines using:
$ grep -E '^\t* ' x86_64-stub.c
Can you please send your patch using git-send-email? It's not
convenient to send in-line comments for a patch sent as attachment.
"if" blocks should be formatted like this:
if (something)
{
..
}
"if" blocks that contain a single line don't need braces. The exception
is if you ou have nested "if" blocks, the outer ones need to have
braces:
if (something)
printf ("Something");
but:
if (something)
{
if (something_else)
printf ("Something 1");
}
else
printf ("Something 2");
Thanks,
Simon
next prev parent reply other threads:[~2020-10-20 13:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BL0PR06MB4418CCCF8597C622AC200C61E1300@BL0PR06MB4418.namprd06.prod.outlook.com>
2020-10-12 17:51 ` [PING] " Battig, Caleb
2020-10-19 14:18 ` [PING][PING] " Battig, Caleb
2020-10-19 14:29 ` Simon Marchi
2020-10-19 14:38 ` Battig, Caleb
2020-10-19 14:43 ` Battig, Caleb
2020-10-19 15:45 ` Simon Marchi
2020-10-19 22:23 ` Battig, Caleb
2020-10-20 13:09 ` Simon Marchi [this message]
2020-10-20 16:34 ` Battig, Caleb
2020-10-22 16:34 ` Battig, Caleb
2020-10-23 0:47 ` Simon Marchi
2020-10-28 22:11 ` Battig, Caleb
2020-11-11 16:39 ` Battig, Caleb
2020-11-11 20:54 ` Simon Marchi
2020-11-11 21:58 ` Battig, Caleb
2020-12-14 15:10 ` 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=074c171f-c4c0-d50f-0b51-c2d3e7e79ad3@simark.ca \
--to=simark@simark.ca \
--cc=Caleb.Battig@netapp.com \
--cc=Stuart.Lovett@netapp.com \
--cc=Wendy.Peikes@netapp.com \
--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