From: Bart Schaefer <schaefer@brasslantern.com> To: "Jun. T" <takimoto-j@kba.biglobe.ne.jp> Cc: Zsh hackers list <zsh-workers@zsh.org> Subject: Re: zargs with -P intermittently failing in zsh 5.9 and macOS Date: Sun, 29 May 2022 13:07:30 -0700 [thread overview] Message-ID: <CAH+w=7bhMmUYnuxArxQ6EosuU450TrTJWAc4d7zkQdcBNuf+kA@mail.gmail.com> (raw) In-Reply-To: <758F3522-3613-435C-B2F6-3FC62220933B@kba.biglobe.ne.jp> Thank you. A couple of concluding remarks ... On Sun, May 29, 2022 at 7:48 AM Jun. T <takimoto-j@kba.biglobe.ne.jp> wrote: > > + /* See if an entry already exists for the pid */ Would it be worthwhile to put that entire thing in #ifdef DEBUG ? Perhaps not, given that the bgstatus_list is unlikely to have many nodes. > - int val = (WIFSIGNALED(status) ? > - 0200 | WTERMSIG(status) : > - (WIFSTOPPED(status) ? > - 0200 | WEXITSTATUS(status) : > - WEXITSTATUS(status))); Irrelevant to the patch, but on the original issue, I keep looking at this and wondering how we got an exit code of 19 rather than 19+128 which would have immediately pointed to SIGCONT. Is this a difference in the way MacOS defines WEXITSTATUS(), or what?
next prev parent reply other threads:[~2022-05-29 20:08 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-24 16:09 Eric Nielsen 2022-05-24 17:32 ` Bart Schaefer 2022-05-24 20:21 ` Eric Nielsen 2022-05-24 20:35 ` Bart Schaefer 2022-05-26 8:57 ` Jun T 2022-05-26 11:21 ` Jun. T 2022-05-27 3:39 ` Bart Schaefer 2022-05-27 4:18 ` Lawrence Velázquez 2022-05-27 5:29 ` Jun T 2022-05-27 16:10 ` Bart Schaefer 2022-05-27 17:25 ` Jun. T 2022-05-29 3:30 ` Bart Schaefer 2022-05-29 14:47 ` Jun. T 2022-05-29 20:07 ` Bart Schaefer [this message] 2022-05-30 11:16 ` Jun T 2022-06-07 6:51 ` Jun T 2022-06-09 2:56 ` Bart Schaefer 2022-06-12 16:43 ` Eric Nielsen
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='CAH+w=7bhMmUYnuxArxQ6EosuU450TrTJWAc4d7zkQdcBNuf+kA@mail.gmail.com' \ --to=schaefer@brasslantern.com \ --cc=takimoto-j@kba.biglobe.ne.jp \ --cc=zsh-workers@zsh.org \ --subject='Re: zargs with -P intermittently failing in zsh 5.9 and macOS' \ /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
Code repositories for project(s) associated with this inbox: https://git.vuxu.org/mirror/zsh/ 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 NNTP newsgroup(s).