Minutes of the 8th November 2018 Teleconference Austin-893 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 9th November 2018 Attendees: Don Cragun, IEEE PASC OR Joerg Schilling, FOKUS Fraunhofer Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Eric Blake, Red Hat Andrew Josey, The Open Group Apologies: Martin Rehak, Oracle, The Open Group OR Mark Ziegast, SHware Systems Dev. * General news None * Outstanding actions (Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 9 March 2018 and earlier) Bug 1077: Recommend support for wide-character regcomp and regexec and/or specify multi-byte behavior OPEN http://austingroupbugs.net/bug_view_page.php?bug_id=1077 Andrew has completed the action to ping his Apple contact and is awaiting a reply. Bug 1122: POSIX should include gettext() and friends OPEN http://austingroupbugs.net/view.php?id=1122 Left open as an action is still in progress to flesh out a complete proposal. * Current Business Bug 1134: Add getentropy interface OPEN http://austingroupbugs.net/view.php?id=1134 Action: Andrew to add boilerplate response regarding a proposal for new interface, and also to ask The Open Group OR if they would sponsor this addition. Both Actions now Completed. (update 19 Oct 2018) There has been no reaction from the Base Working Group and the period for comments has ended now. Bug 1138: Add strsignal(), sig2str() and str2sig() to the standard. OPEN http://austingroupbugs.net/view.php?id=1138 Martin has completed his action. Andrew took an action to chase the Base Working group members for sponsorship of the two interfaces. Update: The action on Andrew is still open. Bug 1141: Add WCOREDUMP(stat) to sys/wait.h Accepted as Marked http://austingroupbugs.net/view.php?id=1141 A comment was received by email during the week. The following change was made to the changes to be made in bugnote:4157. On page 409 line 13896 section , add before WEXITSTATUS:
WCOREDUMP True if WIFSIGNALED is true and creation of a core image was attempted. NOTE: The use of the word "attempted" here means that the process terminated abnormally with actions (see "SIG_DFL" in [xref to 2.4.3 Signal Actions]). A core image might or might not have been produced. Some implementations do not set this bit if a core image was not produced, but this is not a requirement.
The bug is still resolved with Accepted as Marked and Issue8 tag. Bug 0001143: cancellation points: contradiction between base definition and rationale Accepted as Marked http://austingroupbugs.net/view.php?id=1143 An interpretation is required The item is tagged for TC3-2008 Interpretation response: The standard states the requirements for thread cancellation when a timeout occurs, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: The change made as a result of ERN 207 in https://www.opengroup.org/austin/aardvark/latest/xshbug2.txt [^] was intended simply as a clarification as to whether a timeout counts as part of "the event for which it is waiting". However, the change that was made was not quite right, as the "if the thread is suspended at a cancellation point" condition should have applied to the timeout case as well. The point of this part of the standard is that once a function that is a cancellation point has become suspended, then a cancellation request interrupts the suspension and terminates the thread. The function does not perform any further processing as it does not return from suspension, and thus it can assume that once it suspends, cancellation is taken care of and it doesn't need to do any further checking for cancellation. If a cancellation request is made simultaneously with another event that would end the suspension, there is a race and it is unspecified who wins. Notes to the Editor (not part of this interpretation): Change: It is unspecified whether the cancellation request is acted upon or whether the cancellation request remains pending and the thread resumes normal execution if: * The thread is suspended at a cancellation point and the event for which it is waiting occurs * A specified timeout expired before the cancellation request is acted upon. to: It is unspecified whether the cancellation request is acted upon or whether the cancellation request remains pending and the thread resumes normal execution if the thread is suspended at a cancellation point and either: * The event for which it is waiting occurs * A specified timeout expires before the cancellation request is acted upon. Bug 1144: May fmemopen(buf, len, "r") modify the buffer OPEN http://austingroupbugs.net/bug_view_page.php?bug_id=1144 We started to discuss and will continue next time. Next Steps ---------- The next call is on November 15th 2018 (Thursday). There is no call on November 22nd. The next call after that is November 29th. Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/201x-mm-dd username=posix password=2115756#