Wireshark mailing list archives
Re: new dissector - dynamic value string table?
From: Max Baker <max () warped org>
Date: Wed, 27 Feb 2013 08:34:36 -0800
On 02/26/2013 08:32 PM, Hadriel Kaplan wrote:
Can't you use a macro to populate/copy the "common" chunks into separate lists? -hadriel
Hi Hadriel, Good suggestion. I was trying to steer away from this because the cross product is too big. There are about 10 lists and about 10 variants. On the first question of detecting the camera type, it looks like the information I need is captured by packet-usb.c (emem_tree_t *device_to_product_table) -- however it's not exported. I will need to add a way of getting access to this tree from the new dissector. Thanks, -m ___________________________________________________________________________ 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:
- new dissector - dynamic value string table? Max Baker (Feb 26)
- Re: new dissector - dynamic value string table? Guy Harris (Feb 26)
- Re: new dissector - dynamic value string table? Max Baker (Feb 26)
- Message not available
- Re: new dissector - dynamic value string table? Max Baker (Feb 27)
- Re: new dissector - dynamic value string table? Michal.Labedzki (Feb 28)
- Re: new dissector - dynamic value string table? Max Baker (Feb 28)
- Re: new dissector - dynamic value string table? Jakub Zawadzki (Feb 28)
- Re: new dissector - dynamic value string table? Max Baker (Feb 26)
- Re: new dissector - dynamic value string table? Guy Harris (Feb 26)
- Re: new dissector - dynamic value string table? Max Baker (Feb 27)