From: "Julio Guerra" <julio@farjump.io>
To: "Pedro Alves" <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3] Allow using special files with File I/O functions
Date: Wed, 04 Jul 2018 09:44:00 -0000 [thread overview]
Message-ID: <0102016464ad8f06-3019c95a-a2d1-4294-a360-6b436618ea6e-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <cb6729e2-9808-442b-83c9-727afdcdcbf1@redhat.com>
Pedro,
> You can run the testsuite against other remote stubs, not just gdbserver.
> Ideally, you'd set up the testsuite to against your stub. Did you try
> that? I'd recommend that regardless.
>
> Otherwise, even if we only test it when natively run, other folks that have
> embedded stubs that support fileio will end up exercising the test.
I have almost finished writing the tests, but I am struggling on how to
create some special files:
- Creating block or character devices require mknod with root privileges.
- Creating a unix socket is not supported by the TCL library, and
require extra tools (netcat, socat...) to create one from the command line.
Here is what I use for now for the other types:
- Link: TCL function `file link`
- Regular: TCL function `open`
- FIFO pipe command line: `mknod myfifo p` or `mkfifo myfifo` which
doesn't exist on Windows.
What do you suggest? Should I avoid every non portable test cases, which
limits the tests only to links, regular files and directories?
--
Julio Guerra
next prev parent reply other threads:[~2018-07-04 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180628192635.44056-1-julio@farjump.io>
2018-06-28 19:27 ` Julio Guerra
[not found] ` <b725e8cb-4a89-b204-1492-d8af5c76b89f@farjump.io>
2018-06-28 19:31 ` Julio Guerra
2018-06-29 13:42 ` Pedro Alves
[not found] ` <79758ca1-2541-9ae6-d793-b367d6094468@farjump.io>
2018-06-29 14:01 ` Julio Guerra
2018-06-29 14:28 ` Pedro Alves
[not found] ` <6ea235bf-bc87-256a-e745-e54f5e97bf5c@farjump.io>
2018-06-29 14:40 ` Julio Guerra
2018-06-29 15:01 ` Pedro Alves
[not found] ` <817850f4-7ee1-6301-2256-a85b7a9edb02@farjump.io>
2018-07-04 9:44 ` Julio Guerra [this message]
2018-07-05 16:50 ` Pedro Alves
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=0102016464ad8f06-3019c95a-a2d1-4294-a360-6b436618ea6e-000000@eu-west-1.amazonses.com \
--to=julio@farjump.io \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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).