zsh can causes ps to generate error message

Bug #1055551 reported by James Hunt
This bug affects 2 people
Affects Status Importance Assigned to Milestone
procps (Ubuntu)
Fix Released

Bug Description

(ps|grep foo;echo)
Signal 18 (CONT) caught by ps (procps-ng version 3.3.3).
ps:display.c:59: please report this bug

(ps;echo) # works
(ps|grep foo) # works
(ps|grep foo;echo) # fails

This behaviour seems to be caused by zsh since it is not observable using bash. Note too that this bug cannot be recreated on precise.

zsh configuration is stock "system configuration" (run zsh for first time and select option (2) - system defaults).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: zsh 5.0.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Mon Sep 24 16:01:37 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120530)
 PATH=(custom, no user)
SourcePackage: zsh
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
James Hunt (jamesodhunt) wrote :
Revision history for this message
Axel Beckert (xtaran) wrote :

The output "ps:display.c:59: please report this bug" is from procps-ng, so I'd suspect it's rather an issue in procps-ng than in zsh.

The difference to bash is possible caused by differences about when subshells are spawned and when not -- an area where the POSIX specification is ambiguous and hence different behaviour is to be expected.

I can also reproduce this issue with zsh from Debian Experimental (on which Quantal's zsh package is based upon) and with zsh in Debian Unstable and Testing (on which Precise's zsh package is based upon). In those case procps 1:3.3.3-2 where used. But Precise has 1:3.2.8-11ubuntu6, so I guess the difference is rather the procps than the zsh version. Reassigning.

affects: zsh (Ubuntu) → procps (Ubuntu)
Changed in procps (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
taco (halstonc) wrote :

I'm getting the same procps-ng error

$ ps
Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3).
ps:display.c:59: please report this bug
$ dpkg --list procps
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
ii procps 1:3.3.3-2ubuntu5 amd64 /proc file system utilities
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.04
Release: 13.04
Codename: raring

I found a Debian bug report for the same issue (I think).

Can we move to the latest version of procps?

Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :
Revision history for this message
Axel Beckert (xtaran) wrote :

Yes, this does no more appear in at least 16.04 Xenial. And Xenial has procps 3.3.10 which should have fixed this issue. Hence closing. Thanks for the hint.

Changed in procps (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.