Date: Fri, 14 Oct 2016 15:31:08 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-standards@FreeBSD.org Subject: [Bug 213478] procstat --libxo produces non-compliant JSON and XML output Message-ID: <bug-213478-15@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213478 Bug ID: 213478 Summary: procstat --libxo produces non-compliant JSON and XML output Product: Base System Version: 10.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: standards Assignee: freebsd-standards@FreeBSD.org Reporter: dpslavov@hotmail.com Just tried the new functionality for machine readable output of "procstat" = and found two issues with non standard compliant output generated for JSON and = XML formats. Suppose that this is an issue with "libxo" library, not "procstat"= but didn't dig further. For JSON output hexadecimal numbers are printed as normal numbers while JSON standard says that numbers can be only decimal digits, in my opinion they n= eeds to be printed as strings. Here is example output showing the issue: # procstat --libxo:PJ -v 841 { "__version": "1", "procstat": { "vm": { "841": { "process_id": 841, "vm": [ { "kve_start": 0x400000, "kve_end": 0x8f9000, ... For XML output PID is used as name the element while XML element name must start with letter or underscore. Here is an example: <procstat __version=3D"1"> <vm> <841> <process_id>841</process_id> <vm> ... --=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-213478-15>