Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 8955] New: References to invalid preference names don't ge

Date: Sat, 20 Jul 2013 22:16:18 +0000
Bug ID 8955
Summary References to invalid preference names don't get reported as such
Classification Unclassified
Product Wireshark
Version SVN
Hardware All
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Build Information:
TShark 1.11.0 (SVN Rev 50659 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.0, with libpcap, with libz 1.2.5, without
POSIX
capabilities, without libnl, with SMI 0.4.8, without c-ares, without ADNS, with
Lua 5.1, without Python, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT
Kerberos, with GeoIP.

Running on Mac OS X 10.8.3, build 12D78 (Darwin 12.3.0), with locale
en_US.UTF-8, with libpcap version 1.1.1, with libz 1.2.5.
      Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.11.00).

--
If you add to your preferences file a line such as

    ls_payload_display_len: 20

you get a warning such as

    Syntax error in preference ls_payload_display_len (applying your
preferences once should remove this warning)

If you run Wireshark/TShark with a command line option such as

    -o ls_payload_display_len:80

you get an error such as

    tshark: Invalid -o flag "ls_payload_display_len:80"

which, as per

   
http://stackoverflow.com/questions/17757659/how-to-apply-and-override-preferences-with-tshark

can fail to indicate that the problem is that there's no such preference as
"ls_payload_display_len".  (The lack of a "module." in the name should not be
viewed as a syntax error, if that's what's happening here.)


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