| Bug ID |
8272
|
| Summary |
packet-dlm3.c: missing hf[] entries
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
CONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
| CC |
[email protected]
|
Build Information:
--
In packet-dlm3.c there are a number of entries missing from hf_register_info
hf[].
(Found by checkhf)
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_m_lkid
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_m_parent_lkid
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_m_parent_remid
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_m_remid
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_rl_lkid
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_rl_parent_lkid
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_rl_parent_remid
ERROR: NO ARRAY: packet-dlm3.c, hf_dlm3_rl_remid
As noted in checkhf.pl:
## The "NO ARRAY" messages - if accurate - points to an error that will
## cause (t|wire)shark to terminate with an assertion when a packet containing
## this particular element is being dissected.
##
(The issue exists in Wireshark 1.6 & newer).
I've CC'd Masatake YAMATO (the author of the dissector) who I hope can provide
a fix.
(I obtained the EMail address from Bug #5623).
You are receiving this mail because:
- You are watching all bug changes.