🚀 go-pugleaf

Submitted-by: WULKAN@TOROLAB6.VNET.IBM.COM (Mike Wulkan)

I have a question as to the intent of the following statement in section
3.3.1.3 of 1003.1:

  521 (c) The behavior of a process is undefined after it returns normally
  522     from a signal-catching function for a SIGFPE, SIGILL, or SIGSEGV
  523     signal that was not generated by the kill() function or the raise()
  524     function defined by the C Standard {2}.

whereas the ANSI C Standard states in section 4.7.1.1:

  ...  If func executes a return statement and the value of sig was
  SIGFPE or any other implementation-defined value corresponding to a
  computational exception, the behavior is undefined. ...

Is the intent of Posix to "limit" the scope of "other
implementation-defined value" to exactly SIGFPE, SIGILL and SIGSEGV?

Or is Posix simply extending the list to include SIGILL and SIGSEGV
while still allowing for other implementation-defined values?

Mike Wulkan


Volume-Number: Volume 27, Number 3