[Wireshark-dev] Default value for new UAT field

2021-10-14 Thread Uli Heilmeier
With commit d38de4c0 [1] a new field for the I/O graphs UAT has been introduced. With this using io_graphs settings generated with 3.4 (or before) fails in 3.6 [2]. Before releasing 3.6.0 I really want to fix this issue by setting a default value when the field is missing in the io_graphs file.

[Wireshark-dev] Does it make sense to have an FT_BOOLEAN field and > 1 bit set in mask?

2021-10-14 Thread Martin Mathieson via Wireshark-dev
I added this check to tools/check_typed_item_calls.py --mask I am hoping that someone will recognise a protocol they know and check out what is reported, and to be able to work out if this check makes sense to do. Quite a few of the current cases have to do with multi-bit reserved fields, where