Fix: Execution Tracing High-Detail field selection highlighting seemingly wrong bytes...
authorwmeier <wmeier@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 13 Dec 2011 19:54:19 +0000 (19:54 +0000)
committerwmeier <wmeier@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 13 Dec 2011 19:54:19 +0000 (19:54 +0000)
Actual problem:
  A REAL_DATA tvbuff wasn't being added to the "data_sources"
  for a frame. When displaying the frame, when a field referencing the tvb was selected
  for display there was no 'hex bytes' tab for the field and so bytes ended up being
  highlighted in the currently displayed hex bytes tab (thus highlighting bytes in a pane
  not related to the field).

  Consider: Add some code in field creation (proto_tree_add...) to at least warn if
            a field is being created using a tvb whose data_source is not in the
            data_sources list for the frame ?

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@40182 f5534014-38df-0310-8fa8-9805f1628bb7

epan/dissectors/packet-sigcomp.c

index 6356be2c5aeca7d7953a3a61ec6314c5e7263cdb..4d5b44406f9945b9dd80420abe99d39f5cc46ece 100644 (file)
@@ -752,6 +752,7 @@ dissect_sigcomp_common(tvbuff_t *tvb, packet_info *pinfo, proto_tree *sigcomp_tr
             }
 
             udvm_tvb = tvb_new_child_real_data(tvb, buff,state_length+state_address,state_length+state_address);
+            add_new_data_source(pinfo, udvm_tvb, "State/ExecutionTrace");
             /* Arrange that the allocated packet data copy be freed when the
              * tvbuff is freed.
              */