home *** CD-ROM | disk | FTP | other *** search
- Submitted-by: WULKAN@TOROLAB6.VNET.IBM.COM ("Mike Wulkan")
-
- In article <1992Feb26.225705.1510@uunet.uu.net>,
- mib@geech.gnu.ai.mit.edu (Michael I Bushnell) writes:
-
- >If you just do `kill -ILL 387', and process 387 has set the handler
- >for SIGILL to SIG_IGN, truly nothing should happen. I believe Posix
- >should specify this, but I don't believe it does.
- >
- >The confusion here is between the hardware (implementation-defined)
- >event causing the signal and the signal itself.
- >
- >Your suggested fix is not adequate, however. People should be able to
- >catch illegal references in programs, and then be able to exit nicely.
- >Your "fix" precludes doing so portably.
-
- No, my "fix" was only in reference to SIG_IGN. You can still specify
- a signal catching function and then longjmp, exit or abort "nicely".
- There is nothing portable about the current Posix definition of
- ignoring (via SIG_IGN) a SIGSEGV, SIGILL or SIGFPE signal since it
- specifically says that the behavior of the process after the signal
- is delivered is undefined.
-
- Mike Wulkan
-
-
- Volume-Number: Volume 27, Number 19
-
-