Date: Wed, 29 Aug 2012 21:08:34 GMT From: Devin Teske <dteske@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/171174: ps(1) shows bad error message with specific arguments Message-ID: <201208292108.q7TL8Ym4087265@red.freebsd.org> Resent-Message-ID: <201208292110.q7TLA196030152@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 171174 >Category: bin >Synopsis: ps(1) shows bad error message with specific arguments >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Aug 29 21:10:01 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Devin Teske >Release: FreeBSD 10.0-CURRENT amd64 >Organization: FIS Global, Inc. >Environment: FreeBSD ref10-amd64.freebsd.org 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r231914: Sun Feb 19 17:24:37 UTC 2012 bz@glide.freebsd.org:/usr/obj/scratch/src/sys/GLIDE amd64 >Description: Executing "ps -p ''" produces an appropriate error message (shown below): ps: Invalid (zero-length) process id However, when one executes instead "ps -o ucomm -p ''", the error message contains a corrupted string (shown below): ps: Invalid process id: PfÐ >How-To-Repeat: Use the "-o" flag with any value in conjunction with "-p" passed a NULL (zero-length) argument. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208292108.q7TL8Ym4087265>