On HP-UX, don't pretend it was a SIGSEGV when it was a stack overflow.

diff --git a/ChangeLog b/ChangeLog
index f8fc16f8a481f3a62e709ee253fe8c34fd3bd866..14069093248c8d2e4e4e40771ed0c2ed2219a5a9 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2009-01-24  Bruno Haible  <bruno@clisp.org>
+
+       * lib/c-stack.c (segv_handler): If !HAVE_XSI_STACK_OVERFLOW_HEURISTIC,
+       set signo = 0 also if info->si_code <= 0. Needed on HP-UX 11.11.
+       Reported by Gary V. Vaughan <gary@gnu.org>.
+
 2009-01-24  Bruno Haible  <bruno@clisp.org>
 
        * lib/c-strtod.h (c_strtod, c_strtold): Add specification.

diff --git a/lib/c-stack.c b/lib/c-stack.c
index e5e3ab610dc5c45b0adfa9ec0ccd44bb4e494149..d260b47aa546122340ed91ba9e3e4e897c485b4c 100644 (file)
--- a/lib/c-stack.c
+++ b/lib/c-stack.c
@@ -239,21 +239,21 @@ segv_handler (int signo, siginfo_t *info,
              void *context __attribute__ ((unused)))
 {
   /* Clear SIGNO if it seems to have been a stack overflow.  */
-  if (0 < info->si_code)
-    {
 #  if ! HAVE_XSI_STACK_OVERFLOW_HEURISTIC
-      /* We can't easily determine whether it is a stack overflow; so
-        assume that the rest of our program is perfect (!) and that
-        this segmentation violation is a stack overflow.
-
-        Note that although both Linux and Solaris provide
-        sigaltstack, SA_ONSTACK, and SA_SIGINFO, currently only
-        Solaris satisfies the XSI heueristic.  This is because
-        Solaris populates uc_stack with the details of the
-        interrupted stack, while Linux populates it with the details
-        of the current stack.  */
-      signo = 0;
+  /* We can't easily determine whether it is a stack overflow; so
+     assume that the rest of our program is perfect (!) and that
+     this segmentation violation is a stack overflow.
+
+     Note that although both Linux and Solaris provide
+     sigaltstack, SA_ONSTACK, and SA_SIGINFO, currently only
+     Solaris satisfies the XSI heueristic.  This is because
+     Solaris populates uc_stack with the details of the
+     interrupted stack, while Linux populates it with the details
+     of the current stack.  */
+  signo = 0;
 #  else
+  if (0 < info->si_code)
+    {
       /* If the faulting address is within the stack, or within one
         page of the stack end, assume that it is a stack
         overflow.  */
@@ -278,8 +278,8 @@ segv_handler (int signo, siginfo_t *info,
        write (STDERR_FILENO, buf, strlen (buf));
       }
 #   endif
-#  endif
     }
+#  endif
 
   die (signo);
 }