Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Dec 2019 16:00:00 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 242686] procstat usage message is mangled
Message-ID:  <bug-242686-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242686

            Bug ID: 242686
           Summary: procstat usage message is mangled
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: markj@FreeBSD.org

The descriptions of the subcommands are wildly misformatted.  This seems to=
 be
the result of a change in libxo: procstat writes the usage message
incrementally using xo_error(), and libxo recently changed xo_error() to ap=
pend
a newline if the input string does not end with one.

We can fix procstat, but xo_error()'s behaviour contradicts its man page:

     When converting an application to libxo, one can replace
     fprintf(stderr,...) calls with xo_error() calls.

I don't really understand why xo_error() is doing this given that we have
xo_err(), xo_errx(), etc..

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242686-227>