Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: misleading message for SIGFPE
- X-seq: zsh-workers 53120
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: misleading message for SIGFPE
- Date: Tue, 24 Sep 2024 13:03:27 -0700
- Archived-at: <https://zsh.org/workers/53120>
- In-reply-to: <CAH+w=7ZD23odkHK_oFRO0g40AdQx+GMNZ+dhVSQ-Qdw3Gch+vw@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <20240924123652.GA299236@qaa.vinc17.org> <CAH+w=7ZD23odkHK_oFRO0g40AdQx+GMNZ+dhVSQ-Qdw3Gch+vw@mail.gmail.com>
On Tue, Sep 24, 2024 at 11:05 AM Bart Schaefer
<schaefer@xxxxxxxxxxxxxxxx> wrote:
>
> I'm not very familiar with
> usage of siginfo or whether the parent process is able to obtain it
Looks as if this is possible (man 5 siginfo). It appears we'd have to
switch to using waitid(2) for child reaping. However, there doesn't
appear to be a strsignal(3) equivalent of psiginfo(3) to grab the
error message rather than spew it on stderr.
OTOH if there's a reason we're not using strsignal() when it's
available, I've forgotten it.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author