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.
[EMAIL PROTECTED] This test has difficulties being portable, even on platforms
[EMAIL PROTECTED] where syscmd invokes /bin/sh. Kill is not portable with
signal
[EMAIL PROTECTED] names. According to autoconf, the only portable signal
numbers
[EMAIL PROTECTED] are 1 (HUP), 2 (INT), 9 (KILL), 13 (PIPE) and 15 (TERM). But
[EMAIL PROTECTED] all shells handle SIGINT, and ksh handles HUP (as in, the
shell
[EMAIL PROTECTED] exits normally rather than letting the signal terminate it).
[EMAIL PROTECTED] Also, TERM is flaky, as it can also kill the running m4 on
[EMAIL PROTECTED] systems where /bin/sh does not create its own process group.
[EMAIL PROTECTED] 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
[EMAIL PROTECTED]
[EMAIL PROTECTED]
esyscmd(`kill -9 $$')
@result{}
sysval
