aboutsummaryrefslogtreecommitdiffstats
path: root/epan/dissectors/packet-frame.c
diff options
context:
space:
mode:
authorRonnie Sahlberg <ronnie_sahlberg@ozemail.com.au>2005-06-22 08:41:58 +0000
committerRonnie Sahlberg <ronnie_sahlberg@ozemail.com.au>2005-06-22 08:41:58 +0000
commitd9826d34d51a2048a15925025c8e06ecd4e130bb (patch)
tree85bc4695ba037ca3b27ef17b6afd84d69117ca42 /epan/dissectors/packet-frame.c
parent1a663222b4adaf75ce24a1e4f8af3f65f507f54b (diff)
add a dummy variable frame_number to dissect_frame() and assign it the current frame number so that the crashdump that buildbot generates will show which frame the problem occured in.
this is useful since some bugs only trigger ia crash on some platforms. example bug 255 which does not trigger a crash on linux redhat 7.1 svn path=/trunk/; revision=14727
Diffstat (limited to 'epan/dissectors/packet-frame.c')
-rw-r--r--epan/dissectors/packet-frame.c7
1 files changed, 6 insertions, 1 deletions
diff --git a/epan/dissectors/packet-frame.c b/epan/dissectors/packet-frame.c
index 222ad29c7a..2aa4fba4e3 100644
--- a/epan/dissectors/packet-frame.c
+++ b/epan/dissectors/packet-frame.c
@@ -81,8 +81,13 @@ dissect_frame(tvbuff_t *tvb, packet_info *pinfo, proto_tree *parent_tree)
nstime_t ts;
int cap_len = 0, pkt_len = 0;
proto_tree *tree;
- proto_item *item;
+ proto_item *item;
+ int frame_number;
+ frame_number=pinfo->fd->num; /* dummy so that the buildbot crashdumps
+ will show the packetnumber where the
+ crash occured.
+ */
tree=parent_tree;
pinfo->current_proto = "Frame";