Wireshark-bugs: [Wireshark-bugs] [Bug 9272] New: column format strings are only documented in so
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 15 Oct 2013 17:23:03 +0000
Bug ID 9272
Summary column format strings are only documented in source code
Classification Unclassified
Product Wireshark
Version SVN
Hardware All
OS All
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component Documentation
Assignee bugzilla-admin@wireshark.org
Reporter beroset@mindspring.com 

Build Information:
TShark 1.11.0 (SVN Rev 52617 from /trunk)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GLib 2.36.3, with libpcap, with libz 1.2.7, with POSIX
capabilities (Linux), without libnl, without SMI, without c-ares, without ADNS,
with Lua 5.1, without Python, with GnuTLS 3.1.11, with Gcrypt 1.5.3, with MIT
Kerberos, with GeoIP.

Running on Linux 3.11.4-201.fc19.x86_64, with locale en_US.utf8, with libpcap
version 1.4.0, with libz 1.2.7.
       Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz

Built using gcc 4.8.1 20130603 (Red Hat 4.8.1-1).

--
It seems that the only definitive list of column format strings, which are
usable to tshark as command-line arguments, is the source code for column.c. 
These values and their descriptions should be documented in a way that
minimizes the possibility of loss of synchronization between code and
documentation.

It seems that the best way to accomplish that might be by adding a "-G
column-formats" option to tshark and then fixing the documentation to document
this new glossary option.

You are receiving this mail because:
  • You are watching all bug changes.