Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Julio Guerra <julio@farjump.io>
Cc: Pedro Alves <palves@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH 3/4] Explicit fixed-width integral File I/O protocol types
Date: Wed, 02 May 2018 16:14:00 -0000	[thread overview]
Message-ID: <20180502161423.b57daq6zke6yxc63@adacore.com> (raw)
In-Reply-To: <01020163216ed537-dae77402-9d35-42f2-ad27-64c89137aa03-000000@eu-west-1.amazonses.com>

> Since I am talking a lot of embedded software, I CC'd Joel Brobecker
> from AdaCore to maybe give the final direction for a v2.

I'm not really sure what is expected of me, can you clarify? If you
are thinking of my experience with baremetal targets, that's no problem.
But, although I do work with C code on baremetal targets, it tends
to be in situations where we have a C library (based on newlib, for
the most part).

Are we talking about the remote File-IO extension? I should say up front
that my knowledge of this extension was nearly null until I read the
documentation in the manual. I think Pedro is the expert on that.

If I understand correctly, you are arguing that we should be providing
fileio.h so that programs being debugged can use it? I don't understand
how this would integrate with GDB, though. If I understand correctly,
this file is used for the definition of some structures used within
the remote protocol, so the information exchanged between GDB and
GDBserver. How would you exploit that? (what this tells me is that
your patch series deserves a documentation update)

-- 
Joel


  reply	other threads:[~2018-05-02 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28  1:19 [PATCH 0/4] Some File I/O improvements for embedded programming Julio Guerra
2018-04-28  1:19 ` [PATCH 2/4] Do not clear the value of st_dev in File I/O's stat() Julio Guerra
2018-04-28  1:19 ` [PATCH 4/4] Install gdb/fileio.h Julio Guerra
2018-04-28  1:19 ` [PATCH 3/4] Explicit fixed-width integral File I/O protocol types Julio Guerra
2018-05-02 10:46   ` Pedro Alves
     [not found]     ` <332abe88-4b88-3f06-7141-31a798f2b153@farjump.io>
2018-05-02 15:18       ` Julio Guerra
2018-05-02 16:14         ` Joel Brobecker [this message]
     [not found]           ` <a5149a53-09e3-2a08-607a-38d81dfa5eac@farjump.io>
2018-05-02 16:31             ` Julio Guerra
2018-04-28  1:19 ` [PATCH 1/4] Remove the restriction of File I/O functions to regular files only Julio Guerra
2018-04-30  1:54   ` 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=20180502161423.b57daq6zke6yxc63@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=julio@farjump.io \
    --cc=palves@redhat.com \
    --cc=vapier@gentoo.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