https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13984

            Bug ID: 13984
           Summary: "tshark -G ?" doesn't provide expected help
           Product: Wireshark
           Version: 2.4.0
          Hardware: x86-64
                OS: Windows 10
            Status: UNCONFIRMED
          Severity: Normal
          Priority: Low
         Component: TShark
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: christopher.mayn...@igt.com
  Target Milestone: ---

Build Information:
TShark (Wireshark) 2.4.0 (v2.4.0-0-g9be0fa500d)

Compiled (64-bit) with WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with
SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.4.11, with Gcrypt
1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0, with LZ4, with
Snappy, with libxml2 2.9.4.

Running on 64-bit Windows 10, build 14393, with AMD A10-6700 APU with
Radeon(tm)

HD Graphics    (with SSE4.2), with 7368 MB of physical memory, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.4.11, with Gcrypt 1.7.6.

Built using Microsoft Visual C++ 14.0 build 24215
--
Running "tshark -G ?" should provide help about the various report types.  It
does not.  Instead, it just dumps all field information.

tshark.exe -G foo
tshark: Invalid "foo" option for -G flag, enter -G ? for more help.

tshark.exe -G ?
P       Short Frame     _ws.short
P       Malformed Packet        _ws.malformed
P       Unreassembled Fragmented Packet _ws.unreassembled
F       Expert Info     _ws.malformed.dissector_bug     FT_NONE _ws.malformed
        0x0     Dissector bug
F       Expert Info     _ws.malformed.reassembly        FT_NONE _ws.malformed
        0x0     Reassembly error
F       Expert Info     _ws.malformed.expert    FT_NONE _ws.malformed
0x0     Malformed Packet (Exception occurred)
P       Type Length Mismatch    _ws.type_length

...

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to