Wireshark mailing list archives
Re: Modifying custom giop dissector
From: andy.ling () quantel com
Date: Wed, 27 Nov 2013 13:40:40 +0000
mmann78 wrote on 27/11/2013 12:59:17:
So are you generating the dissector and then manually modifying it with your "timecodeString" function?
Yes. If there is a better way I'm all ears. Similarly, some of the INTs are better displayed as hex. I can modify the BASE_DEC to say BASE_HEX, but if there is a better way it would be nice to know.
If so, then I believe you want proto_tree_add_*_format_value Using your example: int s_octet4 = get_CDR_long(tvb,offset,stream_is_big_endian, boundary); proto_tree_add_int_format_value(tree, hf_QuentinTimeline_CombinedTrackSegment_portTimecode, tvb, *offset-4, 4,
octet4, "%s", timecodeString(octet4));
That seems to do the trick (assuming s_octet4 == octet4 or vice versa :-) Thanks Andy Ling ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Modifying custom giop dissector andy . ling (Nov 27)
- Re: Modifying custom giop dissector mmann78 (Nov 27)
- Re: Modifying custom giop dissector andy . ling (Nov 27)
- Re: Modifying custom giop dissector andy . ling (Nov 27)
- Re: Modifying custom giop dissector mmann78 (Nov 27)
- Re: Modifying custom giop dissector andy . ling (Nov 27)
- Re: Modifying custom giop dissector andy . ling (Nov 27)
- Re: Modifying custom giop dissector mmann78 (Nov 27)
- <Possible follow-ups>
- Re: Modifying custom giop dissector mmann78 (Nov 27)
- Re: Modifying custom giop dissector andy . ling (Nov 27)
- Re: Modifying custom giop dissector Guy Harris (Nov 28)