From owner-freebsd-bugs@freebsd.org Tue Jun 27 01:52:52 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27D8FD9903A for ; Tue, 27 Jun 2017 01:52:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0E31273FDE for ; Tue, 27 Jun 2017 01:52:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v5R1qp26077918 for ; Tue, 27 Jun 2017 01:52:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220023] procstat -L only works with corefiles; documentation/code could be tweaked for usability/clarity Date: Tue, 27 Jun 2017 01:52:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ngie@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to bug_status short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2017 01:52:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220023 Ngie Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |ngie@FreeBSD.org Status|New |Open Summary|procstat -L only works with |procstat -L only works with |corefiles ...? |corefiles; | |documentation/code could be | |tweaked for | |usability/clarity --- Comment #2 from Ngie Cooper --- Porting over internal bugzilla comments for context and taking the bug: [reply] [-] Comment 2 Ngie "Hakuna Matata" Cooper 2017-06-26 18:31:03 PDT I'll just fix the documentation since it doesn't state that it should or shouldn't do that, which is a bug. [reply] [-] Comment 3 Conrad Meyer 2017-06-26 18:38:45 PDT I mean, it does say that already: -L Display LWP info for the process pertaining to its signal driv= en exit. ^^^^ ^^^^^^^^^^^= ^^ [reply] [-] Comment 4 Ngie "Hakuna Matata" Cooper 2017-06-26 18:51:08 PDT (In reply to comment #3) > I mean, it does say that already: >=20 > -L Display LWP info for the process pertaining to its signal dr= iven > exit. > ^^^^ ^^^^^^^^^= ^^^^ It's implied, but in a bit of a roundabout way as you noted. Also, the syno= psis suggests that it should be able to take either a pid or a corefile. From https://www.freebsd.org/cgi/man.cgi?query=3Dprocstat&apropos=3D0&sektion=3D= 0&manpath=3DFreeBSD+12-current&arch=3Ddefault&format=3Dhtml : ... procstat [--libxo] [-CHhn] [-w interval] [-b | -c | -e | -f | -i | -j | -k | -l | -L | -r | -s | -S | = -t | -v | -x] [-a | pid | core ...] ... Furthermore, if it's only meant to work with a corefile, the error message I reported in the upstream bug could be clarified by returning the error from kvm_open2, or something similar to that. With mjohnston clarifying the use upstream and after reviewing things a bit more, this is a Trivial item and not a Normal item. What triggered this bug was the fact that I was trying to write tests/manua= lly test out the functionality, and because the documentation wasn't 100% clear= , I filed this bug and committed a few changes upstream to try and help clarify= the feature as best I could. This was one of the areas that wasn't clear to me = that I figured warranted more discussion. --=20 You are receiving this mail because: You are the assignee for the bug.=