https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14957
Guy Harris <g...@alum.mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #9 from Guy Harris <g...@alum.mit.edu> ---
(In reply to Peter Wu from comment #2)
> Should it just set the timestamp to a dummy zero value in the invalid cases?
Not the ideal solution, which would be somehow flagging values as invalid (not
just here, but in other cases, e.g. other type/length mismatches, and strings
that aren't valid in the character encoding they're in), but 1) that's a *much*
bigger change, and requires some annoying changes to the signatures of
functions inside epan/proto.c, as well as handling values marked as "invalid"
in, for example, -T output and 2) it's similar to what we do for other cases
where the length isn't valid for the type - we return *a* value, even if it's
not *the* value.
--
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
