GNU bug report logs - #9473
"kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set

Previous Next

Package: coreutils;

Reported by: shea <at> shealevy.com

Date: Sun, 11 Sep 2011 11:19:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 9473 in the body.
You can then email your comments to 9473 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to owner <at> debbugs.gnu.org, bug-coreutils <at> gnu.org:
bug#9473; Package coreutils. (Sun, 11 Sep 2011 11:19:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to shea <at> shealevy.com:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Sun, 11 Sep 2011 11:19:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: shea <at> shealevy.com
To: bug-coreutils <at> gnu.org
Subject: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set
Date: Sun, 11 Sep 2011 01:25:38 -0700

From http://pubs.opengroup.org/onlinepubs/9699919799/utilities/kill.html:

  When the -l option is specified, the symbolic name of each signal shall
be written in the following
  format:

  "%s%c", <signal_name>, <separator>

  where the <signal_name> is in uppercase, without the SIG prefix, and the
<separator> shall be
  either a <newline> or a <space>. For the last signal written,
<separator> shall be a <newline>.

"kill -l" currently prints a table with each signal preceded by its number
and with the SIG prefixes, even with POSIXLY_CORRECT.
Reply sent to Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility. (Sun, 11 Sep 2011 23:15:02 GMT) Full text and rfc822 format available.
Notification sent to shea <at> shealevy.com:
bug acknowledged by developer. (Sun, 11 Sep 2011 23:15:03 GMT) Full text and rfc822 format available.

Message #10 received at 9473-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: shea <at> shealevy.com
Cc: 9473-done <at> debbugs.gnu.org
Subject: Re: bug#9473: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT
	is	set
Date: Sun, 11 Sep 2011 16:09:49 -0700

Typically, 'kill' is built into the shell, and you're undoubtedly
invoking your shell's version of kill.  So you need to send a bug report
to your shell's maintainer, not to coreutils'.

For example, on my host:

$ /home/eggert/opt/Linux-x86_64/coreutils-8.13/bin/kill -l | head -n 1
HUP
$ kill -l | head -n 1
 1) SIGHUP	 2) SIGINT	 3) SIGQUIT	 4) SIGILL	 5) SIGTRAP

So coreutils conforms, but the shell does not.
Information forwarded to owner <at> debbugs.gnu.org, bug-coreutils <at> gnu.org:
bug#9473; Package coreutils. (Mon, 12 Sep 2011 16:43:02 GMT) Full text and rfc822 format available.

Message #13 received at 9473 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: 9473 <at> debbugs.gnu.org
Cc: eggert <at> cs.ucla.edu
Subject: Re: bug#9473: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT
	is	set
Date: Mon, 12 Sep 2011 18:37:56 +0200

Paul Eggert <eggert <at> cs.ucla.edu> writes:

> So coreutils conforms, but the shell does not.

The shell does, when called as sh (aka bash --posix).

Andreas.

-- 
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 11 Oct 2011 11:24:03 GMT) Full text and rfc822 format available.
This bug report was last modified 13 years and 305 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.