On Sat 15 Feb 2020 at 18:26:25 -0600, Matthew D. Fuller wrote: > So, maybe the m4 process is inheriting our SIG_IGN there, and isn't > prepared for that to be the case? You could try commenting out the
I suspect you have something there: my manual page for sigaction(2)
says:
The execve(2) system call reinstates the default action
for all signals which were caught and resets all signals
to be caught on the user stack. Ignored signals remain
ignored; the signal mask remains the same; signals that
restart pending system calls continue to do so.
-Olaf.
--
Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
___ Anyone who is capable of getting themselves made President should on
\X/ no account be allowed to do the job. --Douglas Adams, "THGTTG"
signature.asc
Description: PGP signature
