Austin Group Defect Tracker

Aardvark Mark IV


Viewing Issue Simple Details Jump to Notes ] Issue History ] Print ]
ID Category Severity Type Date Submitted Last Update
0000629 [1003.1(2008)/Issue 7] System Interfaces Editorial Omission 2012-11-07 09:59 2019-06-10 08:55
Reporter geoffclare View Status public  
Assigned To ajosey
Priority normal Resolution Accepted  
Status Closed  
Name Geoff Clare
Organization The Open Group
User Reference
Section psiginfo
Page Number 1528
Line Number 49319
Interp Status ---
Final Accepted Text
Summary 0000629: psiginfo() description does not mention writing a newline
Description In contrast to the perror() description, the description of psiginfo()
and psignal() on the psiginfo() page does not say explicitly that they
write a newline.

Another less important omission is that the description doesn't say the
message is language-dependent (which perror() does).

Also, the page uses "print" everywhere instead of the more correct "write".

(If anyone tests whether these functions write a newline, note that in
glibc versions up to 2.12 psiginfo() doesn't always write a newline,
but it's a known bug: see
http://www.kernel.org/doc/man-pages/online/pages/man3/psignal.3.html) [^]
Desired Action On line 49313 in the NAME section change "print" to "write".

At line 49319 change:

    The psiginfo() and psignal() functions shall print a message out on
    stderr associated with a signal number. If message is not null and
    is not the empty string, then the string pointed to by the message
    argument shall be printed first, followed by a <colon>, a <space>,
    and the signal description string indicated by signum, or by the
    signal associated with pinfo. If the message argument is null or
    points to an empty string, then only the signal description shall
    be printed. For psiginfo(), the argument pinfo references a valid
    siginfo_t structure. For psignal(), if signum is not a valid signal
    number, the behavior is implementation-defined.

to:

    The psiginfo() and psignal() functions shall write a language-dependent
    message associated with a signal number to the standard error stream
    as follows:

    * First, if message is not a null pointer and is not the empty string,
      the string pointed to by the message argument shall be written,
      followed by a <colon> and a <space>.

    * Then the signal description string associated with signum or with
      the signal indicated by pinfo shall be written, followed by a
      <newline>.

    For psiginfo(), the application shall ensure that the argument pinfo
    references a valid siginfo_t structure. For psignal(), if signum is
    not a valid signal number, the behavior is implementation-defined.
Tags tc2-2008
Attached Files

- Relationships

There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2012-11-07 09:59 geoffclare New Issue
2012-11-07 09:59 geoffclare Status New => Under Review
2012-11-07 09:59 geoffclare Assigned To => ajosey
2012-11-07 09:59 geoffclare Name => Geoff Clare
2012-11-07 09:59 geoffclare Organization => The Open Group
2012-11-07 09:59 geoffclare Section => psiginfo
2012-11-07 09:59 geoffclare Page Number => 1528
2012-11-07 09:59 geoffclare Line Number => 49319
2012-11-07 09:59 geoffclare Interp Status => ---
2012-11-07 16:10 Don Cragun Status Under Review => Resolved
2012-11-07 16:10 Don Cragun Resolution Open => Accepted
2012-11-07 16:10 Don Cragun Desired Action Updated
2012-11-07 16:10 Don Cragun Tag Attached: tc2-2008
2019-06-10 08:55 agadmin Status Resolved => Closed


Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker