Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Mon, 19 Oct 2020 11:45:12 -0400	[thread overview]
Message-ID: <a706660f-c979-6142-0f5b-14dc87f12a4c@simark.ca> (raw)
In-Reply-To: <BL0PR06MB4418C5350E5824D9A913BDF3E11E0@BL0PR06MB4418.namprd06.prod.outlook.com>

On 2020-10-19 10:43 a.m., Battig, Caleb wrote:
> Simon,
>
> Thanks for getting back to me! I resent the original message below. Please let me know if it still hasn't gone through.
>
> The use case of the new x86_64 stub is the same as the old x86 stub, except it works with newer 64-bit processors. See -
> https://sourceware.org/gdb/onlinedocs/gdb/Remote-Stub.html (Notice that there is no 64-bit stub in the list of stubs provided by GDB.)
> https://sourceware.org/gdb/onlinedocs/gdb/Debug-Session.html#Debug-Session
>
> Thanks and let me know if you have any further questions!

Thanks.  I've reached to other maintainers to know what our policy is
today with these files, regarding licensing.  The existing stubs have
been contributed a loooong time ago, so it might have changed.  I'll
let you know.

In the mean time, could you do your best to make the code adhere to our
formatting conventions?  What I spotted mostly:

- Whitespaces: Indentation of 2 columns.  Whole groups of 8 columns
  use a tab, and then spaces are used for the remainder.
- "static" and the return type on their own line:

static void
foo (int bar)
{
  ...
}

- Space before parenthesis in prototypes and calls.

Basically, just look at other files, such as gdb/infrun.c, that will
give you a good idea.

Thanks,

Simon

  reply	other threads:[~2020-10-19 15:45 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 [this message]
2020-10-19 22:23             ` Battig, Caleb
2020-10-20 13:09               ` Simon Marchi
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=a706660f-c979-6142-0f5b-14dc87f12a4c@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