Date: Mon, 14 Nov 2016 18:31:40 +0000 From: "FELLIN, JEFF K \(JEFF\)" <j...@research.att.com> Message-ID: <f79b544255b7b74db4fe1e9b50964335056...@njmtexg5.research.att.com>
| All of the above members MUST be available in all occurrences of | siginfo_t, whether or not they are applicable on a specific signal. What that means is that the siginfo_t cannot become smaller (omitting some of the members when they don't appear to be needed) which would potentially cause a fault when accessing a field that happens not to be present, and which would make it impossible to simply copy one siginfo_t variable to another. | So can someone tell me how this siginfo_t definition matches the minimum set | of members for ALL instances of siginfo_t? I didn't check all of them, but all that I did appear to be there, and if that same siginfo struct is always returned, then all is OK. There's no requirement that the fields contain any kind of meaningful value when they're not defined to have one, or that any two fields (not defined to be both meaningful at the same time) won't occupy the same storage. What were you believing was incorrect about it? kre