From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Peng Yu <pengyu.ut@gmail.com>, Libc-help <libc-help@sourceware.org>
Subject: Re: nonspecific error message
Date: Mon, 29 Mar 2021 13:58:52 -0300 [thread overview]
Message-ID: <3950c909-49c5-bf8c-9695-8eee43f4b667@linaro.org> (raw)
In-Reply-To: <CABrM6w=7YChw_+uCL6stdk50+GSShk7ExGTRq4Y3SxbRSoFDYw@mail.gmail.com>
On 26/03/2021 18:28, Peng Yu via Libc-help wrote:
> Hi,
>
> For renameat2, if only one file is missing, it will perror will print
> "No such file or directory". But this error message is not sufficient
> to determine which file is missing.
>
> How to detail with this kind of case when the error message is
> nonspecific? Should the error be ignored altogether and use some
> customized error message? Or there is some better convention for this
> kind of case?
>
Do you mean once you remove the renameat2.c implementation from source
tree?
prev parent reply other threads:[~2021-03-29 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 21:28 Peng Yu
2021-03-29 16:58 ` Adhemerval Zanella [this message]
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=3950c909-49c5-bf8c-9695-8eee43f4b667@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-help@sourceware.org \
--cc=pengyu.ut@gmail.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).