Comment # 6
on bug 9575
from Chris Maynard
(In reply to comment #5)
> I'd see it as a bug because a command line option ("-e frame.file_off")
> simply isn't honored unless another one ("-o frame.show_file_off=true") is
> given, too.
The command-line option is "being honored"; it's simply that the field isn't
present until you enable the preference. That's just the way Wireshark works.
> If one never uses the GUI (and says to save the preferences), there won't be
> any hint in ~/.wireshark/ either; and the manual page doesn't have
> documentation about the fields and the needed option settings (and doesn't
> want to, and shouldn't, IMO).
The hint would be in the preferences file along with all the other preferences:
# Show offset of frame in capture file
# TRUE or FALSE (case-insensitive)
#frame.show_file_off: FALSE
... as well as the output of running "tshark -G currentprefs" as documented in
the tshark man page.
> For me it's just a violation of do-what-I-say -- if the commandline lists a
> field, any dependencies should just get fulfilled.
Wireshark is doing exactly what you say. The preference is disabled so the
file_off is never added to the tree and thus not present for any packet.
All that being said, it *might* be possible to change Wireshark's behavior so
that if a field is requested that depends on a preference, that the preference
is set to whichever value would allow that field to be displayed ... but that
would be an enhancement to how Wireshark works today. If you wish, you can
file an enhancement bug request for that feature to see if anyone is willing to
modify Wireshark to do this. I have no idea how feasible it would be.
You are receiving this mail because:
- You are watching all bug changes.