gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] gcl_signal


From: Mike Thomas
Subject: [Gcl-devel] gcl_signal
Date: Fri, 25 Jun 2004 17:22:13 +1000

Hi Camm.

As a last minute thought before 2.6.2 marches out the door, what do you
think of these items?

1. in "usig.c"

   EXTER char signals_handled[6];


2. in mingw.h there is this:

#define OTHER_SIGNALS_HANDLED SIGTERM,SIGKILL,SIGABRT,


3. in "usig2.c" we have:

char signals_handled [] = {SIGINT,SIGUSR2,SIGUSR1,SIGIO,SIGALRM,
#ifdef OTHER_SIGNALS_HANDLED
                           OTHER_SIGNALS_HANDLED
#endif
                           0};


(that is, on Windows, eight items + a zero end element - 9 in all compared
to 6 in the declaration in point 1 above) - I'm wondering whether these
things might confuse a compiler?


4. also in "usig.c"

void
install_default_signals(void)
{       gcl_signal(SIGFPE, sigfpe1);
        gcl_signal(SIGPIPE, sigpipe);
        gcl_signal(SIGINT, sigint);
        gcl_signal(SIGUSR1, sigusr1);
        gcl_signal(SIGIO, sigio);
        gcl_signal(SIGALRM, sigalrm);

        /*install_segmentation_catcher(); */
        signals_allowed = sig_normal;
      }

(that is, SIGUSR2 (inserted in signals_handled) is not installed, but
SIGPIPE and SIGFPE (not present in the signals_handled vector) are at least
passed into the function even if not dealt with.)


5. in "main.c" install_segmentation_catcher also runs gcl_signal on SIGSEGV,
which is, also, not present in the signals_handled vector.

Cheers

Mike Thomas.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]