On Wed, Aug 13, 2008 at 06:05:53AM -0600, Eric Blake wrote:
> According to Tom G. Christensen on 8/9/2008 6:41 AM:
> 
> Hello Tom,
> 
> |
> | On Irix 6.5.30 I see gnulib test failures:
> | ./test-c-stack.sh[7]: 12954353 Memory fault(coredump)
> | FAIL: test-c-stack.sh
> | FAIL: test-c-stack2.sh
> 
> Are you in a position to help debug these?  Have you also tried installing
> libsigsegv?
> 
There's a debugger available so with suitable instructions I can help.
New logs for libsigsegv and m4 have been uploaded to http://jupiterrise.com/tmp.
The c-stack test still fails.

> | Compiler is MIPSpro 7.4.4m
> |
> | After fixing the build failure I see these test failures:
> | Bus error - core dumped
> | FAIL: test-c-stack.sh
> 
> Ouch.  It looks like the stack overflow handler is causing unaligned
> access.  Are you in a position to help debug?  Again, have you tried
> libsigsegv?
> 
I have a debugger available so with suitable instructions I can help.
New logs for libsigsegv and m4 have been uploaded to http://jupiterrise.com/tmp.
The c-stack test still fails.

> | Compiler is MIPSpro 7.3.0
> |
> | On Irix 5.3 the compilation fails early:
> | source='fatal-signal.c' object='fatal-signal.o' libtool=no \
> |         DEPDIR=.deps depmode=sgi /bin/ksh ../build-aux/depcomp \
> |         cc  -I.   -I/usr/tgcware/include  -g -c fatal-signal.c
> | cfe: Error: ./sig-handler.h, line 39: 'sa_sigaction' undefined;
> reoccurrences will not be reported.
> |      return (sa_handler_t) a->sa_sigaction;
> 
> Weird.  So Irix 5.3 has sigaction, but not sa_sigaction?  Can you please
> post the definition of struct sigaction from <signal.h>?
> 
>From <sys/signal.h>:
typedef struct sigaction {
        int sa_flags;                   /* see below for values         */
        __sigret_t (*sa_handler)(_sigargs);     /* SIG_DFL, SIG_IGN, or *fn */
        sigset_t sa_mask;               /* additional set of sigs to be */
                                        /* blocked during handler execution */
        int sa_resv[2];
} sigaction_t;

-tgc


Reply via email to