aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUlf Lamping <ulf.lamping@web.de>2005-09-13 08:03:16 +0000
committerUlf Lamping <ulf.lamping@web.de>2005-09-13 08:03:16 +0000
commitde0d7959caf222f8a95443207e0415582c53d0c7 (patch)
tree93402bf9c1ed4f5016a85e40c12d220a28d3356e
parentb1d165da121b094dbe9895da9bd75d059a595dda (diff)
don't simply remove the expert_info output at BoundsError, but add the comment from Guy why this (usually) isn't a bug (because of a short snapshot length).
svn path=/trunk/; revision=15781
-rw-r--r--epan/dissectors/packet-frame.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/epan/dissectors/packet-frame.c b/epan/dissectors/packet-frame.c
index 1c1ef49d0b..7f7e593ab1 100644
--- a/epan/dissectors/packet-frame.c
+++ b/epan/dissectors/packet-frame.c
@@ -275,6 +275,11 @@ show_exception(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree,
col_append_str(pinfo->cinfo, COL_INFO, "[Short Frame]");
item = proto_tree_add_protocol_format(tree, proto_short, tvb, 0, 0,
"[Short Frame: %s]", pinfo->current_proto);
+ /* Don't record BoundsError exceptions as expert events - they merely
+ * reflect a capture done with a snapshot length too short to capture
+ * all of the packet
+ * (any case where it's caused by something else is a bug). */
+ /* expert_add_info_format(pinfo, item, PI_MALFORMED, PI_ERROR, "Short Frame");*/
break;
case ReportedBoundsError: