Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] Dissector bug, protocol SNMP: proto.c:2954: failed asserti

From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Sat, 1 Mar 2008 11:07:25 +0100
On Fri, Feb 29, 2008 at 11:52:53AM -0800, kabbalah74-unsec@xxxxxxxxx wrote:
> Yes this is still happening with 0.99.8 (happening even with the latest build from subversion).
> I'll go ahead a file a bug.

jmayer@egg:~/work/wireshark/svn/trunk/epan/dissectors>
../../tools/checkhf.pl packet-snmp.c | less
jmayer@egg:~/work/wireshark/svn/trunk/epan/dissectors>
../../tools/checkhf.pl packet-snmp.c
Unused entry: packet-snmp.c, hf_snmp_msgSecurityParameters
Unused entry: packet-snmp.c, hf_snmp_msgPrivacyParameters
Unused entry: packet-snmp.c, hf_snmp_msgAuthenticationParameters
Unused entry: packet-snmp.c, hf_snmp_community
Unused entry: packet-snmp.c, hf_snmp_msgAuthoritativeEngineBoots
Unused entry: packet-snmp.c, hf_snmp_datav2u
Unused entry: packet-snmp.c, hf_snmp_identity
Unused entry: packet-snmp.c, hf_smux_version
Unused entry: packet-snmp.c, hf_snmp_non_repeaters
Unused entry: packet-snmp.c, hf_snmp_description
Unused entry: packet-snmp.c, hf_snmp_enterprise
Unused entry: packet-snmp.c, hf_snmp_msgAuthoritativeEngineID
Unused entry: packet-snmp.c, hf_snmp_max_repetitions
Unused entry: packet-snmp.c, hf_snmp_valueType
Unused entry: packet-snmp.c, hf_smux_pdutype
Unused entry: packet-snmp.c, hf_snmp_data
Unused entry: packet-snmp.c, hf_snmp_msgUserName
Unused entry: packet-snmp.c, hf_snmp_msgGlobalData
Unused entry: packet-snmp.c, hf_snmp_time_stamp
NO ARRAY: packet-snmp.c, hf_snmp_big_counter_value
Unused entry: packet-snmp.c, hf_snmp_name
Unused entry: packet-snmp.c, hf_snmp_password
Unused entry: packet-snmp.c, hf_snmp_operation
Unused entry: packet-snmp.c, hf_snmp_contextName
Unused entry: packet-snmp.c, hf_snmp_version
Unused entry: packet-snmp.c, hf_snmp_variable_bindings
Unused entry: packet-snmp.c, hf_snmp_msgAuthoritativeEngineTime
Unused entry: packet-snmp.c, hf_snmp_subtree
Unused entry: packet-snmp.c, hf_snmp_msgID
Unused entry: packet-snmp.c, hf_snmp_generic_trap
Unused entry: packet-snmp.c, hf_snmp_bulkPDU_request_id
Unused entry: packet-snmp.c, hf_snmp_msgMaxSize
Unused entry: packet-snmp.c, hf_snmp_error_status
Unused entry: packet-snmp.c, hf_snmp_specific_trap
Unused entry: packet-snmp.c, hf_snmp_error_index
Unused entry: packet-snmp.c, hf_snmp_contextEngineID
Unused entry: packet-snmp.c, hf_snmp_msgVersion
Unused entry: packet-snmp.c, hf_snmp_request_id
Unused entry: packet-snmp.c, hf_snmp_smux_version
Unused entry: packet-snmp.c, hf_snmp_msgData
Unused entry: packet-snmp.c, hf_snmp_msgFlags
Unused entry: packet-snmp.c, hf_snmp_priority
Unused entry: packet-snmp.c, hf_snmp_msgSecurityModel
Unused entry: packet-snmp.c, hf_snmp_agent_addr
Unused entry: packet-snmp.c, hf_snmp_parameters
Unused entry: packet-snmp.c, hf_snmp_VarBindList_item

It's the NO ARRAY line that shows the problem.

 Ciao
      Joerg

-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.