Wireshark-bugs: [Wireshark-bugs] [Bug 9548] New: tshark prints out wrong error string for name r

Date: Wed, 11 Dec 2013 09:32:57 +0000
Bug ID 9548
Summary tshark prints out wrong error string for name resolv options
Classification Unclassified
Product Wireshark
Version SVN
Hardware All
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component TShark
Assignee [email protected]
Reporter [email protected]

Created attachment 12289 [details]
Proposed fix for name-resolv error string

Build Information:
TShark 1.11.3 (SVN Rev 53931 from /trunk)

Copyright 1998-2013 Gerald Combs <[email protected]> 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, with SMI 0.4.8, with c-ares 1.10.0, with
Lua 5.1, without Python, with GnuTLS 3.1.16, with Gcrypt 1.5.3, with MIT
Kerberos, with GeoIP.

Running on Linux 3.11.9-200.fc19.x86_64, with locale en_US.UTF-8, with libpcap
version 1.4.0, with libz 1.2.7.
       Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz

Built using gcc 4.8.2 20131017 (Red Hat 4.8.2-1).

--
tshark -N <wrong argument> prints out wrong error string, which lacks 'N'
option. The problem is related to tshark.c; man page talks about all 5 options.

Actual results:

tshark: -N specifies unknown resolving option 'r'; 
           Valid options are 'm', 'n', 't', and 'C'

Expected results:

tshark: -N specifies unknown resolving option 'r';
           Valid options are 'm', 'n', 'N', 't', and 'C'


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