Comment # 9
on bug 11322
from Pascal Quantin
The current code does not seem to have triggered any issue with all the
existing builtin dissectors since a year, so maybe I'm missing something.
Right now when dissector_try_uint_new returns 0, we seem to consider that the
packet was rejected by the dissector registered on that port:
/* Look for a given value in a given uint dissector table and, if found,
call the dissector with the arguments supplied, and return the number
of bytes consumed, otherwise return 0. */
WS_DLL_PUBLIC int dissector_try_uint_new(dissector_table_t sub_dissectors,
const guint32 uint_val, tvbuff_t *tvb, packet_info *pinfo, proto_tree
*tree, const gboolean add_proto_name, void *data);
SO I find it odd to have a dissector that acknowledges a packet as being for it
still returning 0: how can the caller can make the difference between an
existing and non existing sub dissector?
You are receiving this mail because:
- You are watching all bug changes.