Wireshark mailing list archives
Re: Modifying custom giop dissector
From: andy.ling () quantel com
Date: Wed, 27 Nov 2013 16:36:15 +0000
If your type is FT_INT64 you use proto_tree_add_int64[_format_value] If your type is FT_UINT64 you use proto_tree_add_uint64[_format_value] Same is true for 32-bit values- signed and unsigned types have different
APIs.
OK, thanks, that fixes it. I must have been lucky with the 32 bit ones. I guess they were defined in the IDL as unsigned. It does seem odd that the data specifies the type and then you have to call a type specific function. I assume as nobody has replied, there isn't an easier way than editing the output of omniorb. It would be nice if there was a way of adding some formatting hints in the IDL comments or something like that. Regards 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)