From: Julio Guerra <guerr@julio.in>
To: gdb-patches@sourceware.org
Cc: Mike Frysinger <vapier@gentoo.org>
Subject: [PATCH 1/4] Remove the restriction of File I/O functions to regular files only
Date: Sat, 28 Apr 2018 01:19:00 -0000 [thread overview]
Message-ID: <20180428011940.115515-2-julio@farjump.io> (raw)
In-Reply-To: <20180428011940.115515-1-julio@farjump.io>
The major goal is being able to write advanced embedded testing functions, like:
- reading/writing to a dedicated fifo between the embedded program and the host,
instead of using the GDB console only.
- mocking features based on host's.
Tested with https://github.com/farjump/raspberry-pi/blob/ea31c48d7c7eed27d39fb1bec2d3a1d308cb8ae7/src/semihosting/semihosting.c
Also answers to an old RFC I did on the ML: https://sourceware.org/ml/gdb/2016-07/msg00003.html
2018-04-28 Julio Guerra <julio@farjump.io>
* gdb/remote-fileio.c: allow using File I/O functions with special
files.
Signed-off-by: Julio Guerra <julio@farjump.io>
---
gdb/ChangeLog | 5 +++++
gdb/remote-fileio.c | 24 ------------------------
2 files changed, 5 insertions(+), 24 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 55e640581a..a9ddac5f98 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2018-04-28 Julio Guerra <julio@farjump.io>
+
+ * gdb/remote-fileio.c: allow using File I/O functions with special
+ files.
+
2018-04-27 Alexandre Oliva <aoliva@redhat.com>
* compile/compile-c-types.c (convert_int, convert_float):
diff --git a/gdb/remote-fileio.c b/gdb/remote-fileio.c
index 4c648a9c83..fa3cb15033 100644
--- a/gdb/remote-fileio.c
+++ b/gdb/remote-fileio.c
@@ -407,24 +407,6 @@ remote_fileio_func_open (char *buf)
return;
}
- /* Check if pathname exists and is not a regular file or directory. If so,
- return an appropriate error code. Same for trying to open directories
- for writing. */
- if (!stat (pathname, &st))
- {
- if (!S_ISREG (st.st_mode) && !S_ISDIR (st.st_mode))
- {
- remote_fileio_reply (-1, FILEIO_ENODEV);
- return;
- }
- if (S_ISDIR (st.st_mode)
- && ((flags & O_WRONLY) == O_WRONLY || (flags & O_RDWR) == O_RDWR))
- {
- remote_fileio_reply (-1, FILEIO_EISDIR);
- return;
- }
- }
-
fd = gdb_open_cloexec (pathname, flags, mode);
if (fd < 0)
{
@@ -885,12 +867,6 @@ remote_fileio_func_stat (char *buf)
remote_fileio_return_errno (-1);
return;
}
- /* Only operate on regular files and directories. */
- if (!ret && !S_ISREG (st.st_mode) && !S_ISDIR (st.st_mode))
- {
- remote_fileio_reply (-1, FILEIO_EACCES);
- return;
- }
if (statptr)
{
host_to_fileio_stat (&st, &fst);
--
2.17.0
next prev parent reply other threads:[~2018-04-28 1:19 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 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
[not found] ` <a5149a53-09e3-2a08-607a-38d81dfa5eac@farjump.io>
2018-05-02 16:31 ` Julio Guerra
2018-04-28 1:19 ` Julio Guerra [this message]
2018-04-30 1:54 ` [PATCH 1/4] Remove the restriction of File I/O functions to regular files only Simon Marchi
2018-04-28 1:19 ` [PATCH 2/4] Do not clear the value of st_dev in File I/O's stat() Julio Guerra
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=20180428011940.115515-2-julio@farjump.io \
--to=guerr@julio.in \
--cc=gdb-patches@sourceware.org \
--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