diff options
| author | Guy Harris <guy@alum.mit.edu> | 2014-12-08 15:36:26 -0800 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2014-12-08 23:36:58 +0000 |
| commit | 32e1ff9bf35fe1990536130e104f9f49ef65981b (patch) | |
| tree | b328f0ccb86f30b07597d87660acc96475f03133 | |
| parent | ffcacae8b39456e84de2c88cdbd81ed940425d1c (diff) | |
Don't put bitmasks under an FT_NONE.
proto_tree_add_bitmask() requires that the field under which it's
putting the bitmasks be an FT_INTn or FT_UINTn, so that it can determine
the length of the field.
Arguably, proto_tree_add_bitmask() should, instead, take a length
argument, just as other proto_tree_add_ routines do, and, arguably, we
should perhaps not even have FT_UINTn and FT_INTn, just FT_UINT and
FT_INT, with the display width for hex and octal (leading zeroes)
determined by the actual length of the field or something such as that,
or as part of the field that also contains the base.
But, even with that, we might want to require an FT_UINTn or FT_INTn
anyway, at least in cases where the value of the field as a whole is
interesting.
Change-Id: I4dff8fb1686a30b7d145c089dd1be7f96ecf23e0
Reviewed-on: https://code.wireshark.org/review/5680
Reviewed-by: Guy Harris <guy@alum.mit.edu>
| -rw-r--r-- | epan/dissectors/packet-dvmrp.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/epan/dissectors/packet-dvmrp.c b/epan/dissectors/packet-dvmrp.c index 10bdfa0f59..59293b661d 100644 --- a/epan/dissectors/packet-dvmrp.c +++ b/epan/dissectors/packet-dvmrp.c @@ -778,7 +778,7 @@ proto_register_dvmrp(void) VALS(code_v3), 0, "DVMRP Packet Code", HFILL }}, { &hf_capabilities, - { "Capabilities", "dvmrp.capabilities", FT_NONE, BASE_NONE, + { "Capabilities", "dvmrp.capabilities", FT_UINT8, BASE_HEX, NULL, 0, "DVMRP V3 Capabilities", HFILL }}, {&hf_cap_leaf, |