Fix: value string specified as a BASE_VAL64_STRING in

 an hf[] entry but defined as a 'value_string' intead of
 as a 'val64_string'.

Caused 'tshark -G values' to crash
 (and presumably would also cause a crash when the value-string
  is referenced in a dissection):

Introduced in svn #54728

(Note: There's still another 'tshark -G values' crash to to found & fixed)

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@54983 f5534014-38df-0310-8fa8-9805f1628bb7

diff --git a/epan/dissectors/packet-bgp.c b/epan/dissectors/packet-bgp.c
index f6817dddd7a7f8609f2a857a55d5ef1da5fc6a4a..64d4c4d631cafe10a8451aaea780af0cef435b63 100644 (file)
--- a/epan/dissectors/packet-bgp.c
+++ b/epan/dissectors/packet-bgp.c
@@ -807,7 +807,7 @@ static const value_string link_state_nlri_protocol_id_values[] = {
 };
 
 /* Link-State routing universes */
-static const value_string link_state_nlri_routing_universe_values[] = {
+static const val64_string link_state_nlri_routing_universe_values[] = {
         {BGP_LS_NLRI_ROUTING_UNIVERSE_LEVEL_3, "L3 packet topology" },
         {BGP_LS_NLRI_ROUTING_UNIVERSE_LEVEL_1, "L1 optical topology"},
         {0, NULL}