Changes to m4/doc/m4.texinfo,v [branch-1_4]

[Eric Blake]

CVSROOT:        /sources/m4
Module name:    m4
Branch:         branch-1_4
Changes by:     Eric Blake <ericb>      06/07/19 18:16:24

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.1.1.1.2.50
retrieving revision 1.1.1.1.2.51
diff -u -b -r1.1.1.1.2.50 -r1.1.1.1.2.51
--- doc/m4.texinfo      19 Jul 2006 14:55:53 -0000      1.1.1.1.2.50
+++ doc/m4.texinfo      19 Jul 2006 18:16:23 -0000      1.1.1.1.2.51
@@ -3737,14 +3737,23 @@
 is terminated by a signal, rather than a normal exit, the result is the
 signal number shifted left by eight bits.
 
address@hidden This test has difficulties being portable, even on platforms
address@hidden where syscmd invokes /bin/sh.  Kill is not portable with signal
address@hidden names.  According to autoconf, the only portable signal numbers
address@hidden are 1 (HUP), 2 (INT), 9 (KILL), 13 (PIPE) and 15 (TERM).  But
address@hidden all shells handle SIGINT, and ksh handles HUP (as in, the shell
address@hidden exits normally rather than letting the signal terminate it).
address@hidden Also, TERM is flaky, as it can also kill the running m4 on
address@hidden systems where /bin/sh does not create its own process group.
address@hidden That leaves KILL and PIPE as the two signals tested.
 @example
 dnl This test assumes kill is a shell builtin, and that signals are
 dnl recognizable.
 ifdef(`__unix__', , `m4exit(`77')')dnl
-syscmd(`kill -1 $$')
+syscmd(`kill -13 $$')
 @result{}
 sysval
address@hidden
address@hidden
 esyscmd(`kill -9 $$')
 @result{}
 sysval