From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) by sourceware.org (Postfix) with ESMTPS id 2EB133851416 for ; Mon, 29 Mar 2021 16:58:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2EB133851416 Received: by mail-qv1-xf31.google.com with SMTP id t16so6758222qvr.12 for ; Mon, 29 Mar 2021 09:58:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=yEkxEr9msVfUrpCcuzQI8nauSz4Sa6imkwgVUDg7ekk=; b=YfWltBuEVqHdU+kWZ2TlQC1tf5PJ7V/dLobyX9YmGW4N772F2qx8jX5heSnKaY/ySk hf452YB5mDYVrsX5EgrV0x92GfzEt6KQ97A5iKaK/WIMWqRiJKAAZFWaGMGmh/lISO/J GfqLjs8JcynFAbseoa1zO158PKfngGyTtAr47dP2eBXjkIazUL3w2d4dCroy+ghdK5eG muI3ll2y3x2JFd9h9mXGDv2TV2pzR0j9iUAWtUUrCFxGLXNG2vijqY11KJD9h8fVRb/l UfLQJrPOyGW3+LFHHfMsw+Mr2dMYQ27D+CPRh4NmxzpJACxlCmNnW65cQufce8eIoBlj BKkA== X-Gm-Message-State: AOAM532l75Z7wrJ3Shgh00ouJIZYc7hAc0HP1LP7yZIc6KhUmUcynoCm yfYSeoiew/dK0kiUAbU1bqq0Mu63jATL9j93 X-Google-Smtp-Source: ABdhPJxf8/HPr7YaO2oAo0oeonoYRm85W+juv7vdan+XY9oPlr7QTUA372JeSxrh+lHayGzozsJw9Q== X-Received: by 2002:a05:6214:1051:: with SMTP id l17mr26224674qvr.49.1617037135212; Mon, 29 Mar 2021 09:58:55 -0700 (PDT) Received: from [192.168.1.132] ([177.194.41.149]) by smtp.gmail.com with ESMTPSA id j30sm11475407qtv.90.2021.03.29.09.58.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 29 Mar 2021 09:58:54 -0700 (PDT) Subject: Re: nonspecific error message To: Peng Yu , Libc-help References: From: Adhemerval Zanella Message-ID: <3950c909-49c5-bf8c-9695-8eee43f4b667@linaro.org> Date: Mon, 29 Mar 2021 13:58:52 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2021 16:58:57 -0000 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?