[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Confusing "Success" error message
From: |
Andries E. Brouwer |
Subject: |
Re: Confusing "Success" error message |
Date: |
Mon, 4 Nov 2019 13:57:54 +0100 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Mon, Nov 04, 2019 at 12:19:33AM +0100, Darshit Shah wrote:
> Hi Francesco,
>
> This issue has indeed been reported multiple times in the past. While it is
> confusing, the text "Success" is out of our hands. It is the value of
> `perror()` after we encounter that a system call resulted in the error.
The value of errno does not live long. After any library call
it can be destroyed. So the code in http.c
case FWRITEERR: case FOPENERR:
/* Another fatal error. */
logputs (LOG_VERBOSE, "\n");
logprintf (LOG_NOTQUIET, _("Cannot write to %s (%s).\n"),
quote (hstat.local_file), strerror (errno));
seems broken. The value of errno must be saved if its value is needed later.
- Confusing "Success" error message, Francesco Turco, 2019/11/03
- Re: Confusing "Success" error message, Darshit Shah, 2019/11/03
- Re: Confusing "Success" error message,
Andries E. Brouwer <=
- Re: Confusing "Success" error message, Tim Rühsen, 2019/11/07
- Re: Confusing "Success" error message, Andries E. Brouwer, 2019/11/07
- Re: Confusing "Success" error message, Tim Rühsen, 2019/11/08
- Re: Confusing "Success" error message, Francesco Turco, 2019/11/08
- Re: Confusing "Success" error message, Francesco Turco, 2019/11/08
- Re: Confusing "Success" error message, Andries E. Brouwer, 2019/11/08
- Re: Confusing "Success" error message, Eli Zaretskii, 2019/11/08
- Re: Confusing "Success" error message, Andries E. Brouwer, 2019/11/08
- Re: Confusing "Success" error message, Eli Zaretskii, 2019/11/08
- Re: Confusing "Success" error message, Andries E. Brouwer, 2019/11/08