Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: hppa problems
- X-seq: zsh-workers 14842
- From: Clint Adams <clint@xxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: hppa problems
- Date: Mon, 11 Jun 2001 09:59:14 -0400
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <1010611030425.ZM21914@xxxxxxxxxxxxxxxxxxxxxxx>; from schaefer@xxxxxxxxxxxxxxxxxxxxxxx on Mon, Jun 11, 2001 at 03:04:25AM +0000
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20010610070719.A4521@xxxxxxxx> <20010610081031.C4640@xxxxxxxx> <1010610163423.ZM21625@xxxxxxxxxxxxxxxxxxxxxxx> <20010610191043.A17968@xxxxxxxx> <20010610201920.A18831@xxxxxxxx> <1010611030425.ZM21914@xxxxxxxxxxxxxxxxxxxxxxx>
> That's almost certainly not supposed to happen. Can you track it down
> any further? It looks like it's happening when the handler() function
> is called. What's the prototype for `sa_handler' in struct sigaction
> supposed to be?
struct sigaction
{
/* Signal handler. */
#ifdef __USE_POSIX199309
union
{
/* Used if SA_SIGINFO is not set. */
__sighandler_t sa_handler;
/* Used if SA_SIGINFO is set. */
void (*sa_sigaction) (int, siginfo_t *, void *);
}
__sigaction_handler;
# define sa_handler __sigaction_handler.sa_handler
# define sa_sigaction __sigaction_handler.sa_sigaction
#else
__sighandler_t sa_handler;
#endif
/* Special flags. */
unsigned long int sa_flags;
/* Additional set of signals to be blocked. */
__sigset_t sa_mask;
};
#define SA_SIGINFO 0x00000010 /* Invoke signal-catching function with
three arguments instead of one. */
and
typedef void (*__sighandler_t) (int);
Messages sorted by:
Reverse Date,
Date,
Thread,
Author