public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Julio Guerra" <julio@farjump.io>
To: "Tom Tromey" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"Pedro Alves" <palves@redhat.com>
Subject: Re: [PATCH] Install fileio.h to share File I/O protocol type definitions
Date: Wed, 25 Jul 2018 20:01:00 -0000	[thread overview]
Message-ID: <01020164d3075dd7-c5101668-597f-4dd0-81ef-d7a1bc2642fc-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <87o9evyump.fsf@tromey.com>

Le 25/07/2018 à 21:37, Tom Tromey a écrit :
>>>>>> "Julio" == Julio Guerra <julio@farjump.io> writes:
> Your message had ^M characters at the end of each line - no big deal but
> please make sure this isn't what would appear an eventual push.

I am not sure to understand where did you saw ^M chars? I used git
format-patch + send-email as usually, I don't understand where they
could come from.

> Julio> Prevent remote programs from redefining File I/O protocol types by installing
> Julio> include/gdb/fileio.h to share its type definitions.
>
> This seems reasonable enough, but what is it you plan to use it for?
> (I could guess I suppose but it seemed better to ask.)

When you implement gdb stubs supporting the File I/O protocol, the
remote programs then using File I/O services will require those types.
Right now, we have to define them ourselves, but by installing this
file, we could firstly stop redefining them, and secondly, have some
kind of single source of truth as it's easy to do mistakes when
redefining them (actually, our struct stat redefinition was wrong for
years, but no one was using it until now).

> It seems like it would be a good idea to have some documentation for
> this, if it's something we intend to support.

The documentation already talks about these types here
https://sourceware.org/gdb/onlinedocs/gdb/Protocol_002dspecific-Representation-of-Datatypes.html#Protocol_002dspecific-Representation-of-Datatypes
But do you want me to add some documentation about this file being
installed before the list?

-- 
Julio Guerra


  parent reply	other threads:[~2018-07-25 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180709093410.63068-1-julio@farjump.io>
2018-07-09  9:34 ` Julio Guerra
2018-07-25 19:37   ` Tom Tromey
     [not found]     ` <9f54db97-2e20-1935-c730-e6036a5809e0@farjump.io>
2018-07-25 20:01       ` Julio Guerra [this message]
2018-09-07 22:08         ` Tom Tromey

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=01020164d3075dd7-c5101668-597f-4dd0-81ef-d7a1bc2642fc-000000@eu-west-1.amazonses.com \
    --to=julio@farjump.io \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).