Hi enh, On 2023-09-13 21:58, enh wrote: > is it a requirement that the 3p pages only contain text that's > explicitly in POSIX? Yes, I guess. > the siginfo_t::si_addr description on > system_data_types.7 (which is what people see if they `man siginfo_t`) > says "Address of faulting instruction", which isn't true for all > signals, and caused enough confusion for the ART maintainers that they > came to me as Android's libc maintainer for an adjudication. meanwhile > the sigaction.2 page says "Memory location which caused fault" which > seems much more helpful. siginfo_t(3type), aka system_data_types(7), isn't a POSIX page, so we can patch it if you want. I'd also move the types to their own pages and have system_data_types(7) be a link to intro(3) (until we have an intro(3type)). > > i _was_ going to send you a patch, but then i checked > https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/signal.h.html > which has the same unfortunate "Address of faulting instruction" > wording. at which point i assume you want me to file an Austin Group > bug (which i'll do anyway: > https://www.austingroupbugs.net/view.php?id=1775), Thanks. > and presumably wait > for POSIX's wording to improve before changing system_data_types.7? Nah, we can improve siginfo_t(3type) already. Feel free to send a patch. Cheers, Alex -- <http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature