Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
RE: Re: [PATCH] Fix a bunch of Coverity-reported defects
- X-seq: zsh-workers 52251
- From: zeurkous@xxxxxxxxxxxxxxx
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, Mikael Magnusson <mikachu@xxxxxxxxx>
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: RE: Re: [PATCH] Fix a bunch of Coverity-reported defects
- Date: Thu, 26 Oct 2023 14:42:04 +0000 (UTC)
- Archived-at: <https://zsh.org/workers/52251>
- In-reply-to: <CAH+w=7YnOxFCgWXqPwK36VyrZJRP-R1MGUHYc8cZECLxO-Jd6A@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <CAH+w=7a88XNokfYdU4kfbNUAOn_bPPYw1zoRR0im-js_xRWwHQ@mail.gmail.com> <CAHYJk3TE5cQ+f8=mvvQ=CxppfMRKhRh2boz7PWRyoexFWcrSYQ@mail.gmail.com> <CAH+w=7YnOxFCgWXqPwK36VyrZJRP-R1MGUHYc8cZECLxO-Jd6A@mail.gmail.com>
On Thu, 26 Oct 2023 07:25:27 -0700, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> Many others were about not checking error status of system calls when
> in practice there's no sensible recovery mode, e.g., what would we do
> instead if setting the close-on-exec flag on an fd does not work?
Fail hard; at the very least, it should be warn(3)'d about.
--zeurkous.
--
Friggin' Machines!
Messages sorted by:
Reverse Date,
Date,
Thread,
Author