home *** CD-ROM | disk | FTP | other *** search
- Submitted-by: rcollins@encore.com (Roger Collins)
-
- wulkan@vnet.ibm.com (Mike Wulkan) writes:
- >In .1 section 3.3.1.2 it says:
- > "If the action associated with a blocked signal is anything other
- > than to ignore the signal, and if that signal is generated for the
- > process, the signal shall remain pending until either it is unblocked
- > or the action associated with it is set to ignore the signal."
- >To me this implies that a synchronous signal, such as a hardware fault,
- >would not be held pending if it is blocked, because it was not generated
- >for the process.
-
- I disagree. In .1 there is no concept of thread, so any signal to that
- thread or process is "for the process."
-
- >However in .4a 8.3.3.2 it says:
-
- > "Signals which are generated by some action attributable to a particular
- > thread, such as a hardware fault, shall be delivered to the thread that
- > caused the signal to be generated."
- > ...
- > "If the receiving thread has blocked delivery of the signal, the
- > signal remains pending on the thread until the thread unblocks
- > delivery of the signal or the action associated with the signal is
- > set to ignore the signal."
- >.4a seems to have disregarded the difference between an asynchronous
- >pthread_kill() and a synchronous signal, such as a hardware fault.
-
- Yes, I'll agree with this.
-
- >Unless I'm missing something, it would seem that .1 and .4a are
- >incompatible with regards to keeping or not keeping synchronously
- >generated (blocked) signals pending.
-
- No, I think it is consistent when you allow for the loose usage of
- process in .1 because there is no thread concept in that standard.
- Synchronous and asynchronous signals should stay pending (until blah
- blah blah).
-
- >Can someone tell me what the "correct" interpretation is?
-
- That's *my* interpretation -- better than correct. :)
-
- Roger Collins
-
-
- Volume-Number: Volume 31, Number 4
-
-