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. -----Original Message----- From: andy.ling <[email protected]> To: Developer support list for Wireshark <[email protected]> Sent: Wed, Nov 27, 2013 11:12 am Subject: Re: [Wireshark-dev] Modifying custom giop dissector > > 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. > Is this supposed to work for 64 bit numbers? I have an entry that looks like {&hf_Quentin_RushIdent_first, {"RushIdent_first","giop-q_quentin.RushIdent.first",FT_INT64,BASE_DEC,NULL,0x0,NULL,HFILL}}, If I change it to FT_UINT64 & BASE_HEX I get an error in the dissector Message: proto.c:3258: failed assertion "hfinfo->type == FT_INT64" Making a similar change to variables that are FT_INT32 seems to work as expected. Thanks for any help Andy Ling ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
