This is probably best reported as a bug on the Wireshark Bugzilla:
http://bugs.wireshark.org/
That makes it easier for others to find the problem (and avoid submitting a
duplicate), and provides us with a way to track the fix process (and find it
when generating the release notes if it's fixed in the new release).
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
