Wireshark mailing list archives
Re: Troubles with ASN generated code
From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Sat, 20 May 2017 23:03:38 +0200
On 19-05-17 19:44, Guy Harris wrote:
For example, if libwireshark exports a value_string table, I'm not sure all the platforms we support would allow a plugin dissector to point to that value_string from one of its header fields.
I think we're seeing that with TFS (true/false strings). We have a collection of them ready for use in tfs.[ch], but these appear to be unusable in (dissector) plugins on Windows. Thanks, Jaap ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Troubles with ASN generated code Jaap Keuter (May 18)
- Re: Troubles with ASN generated code Guy Harris (May 18)
- Re: Troubles with ASN generated code Jaap Keuter (May 19)
- Re: Troubles with ASN generated code Guy Harris (May 19)
- Re: Troubles with ASN generated code Jaap Keuter (May 20)
- Re: Troubles with ASN generated code Graham Bloice (May 21)
- Re: Troubles with ASN generated code Guy Harris (May 21)
- Re: Troubles with ASN generated code Graham Bloice (May 21)
- Re: Troubles with ASN generated code Guy Harris (May 21)
- Re: Troubles with ASN generated code Graham Bloice (May 21)
- Re: Troubles with ASN generated code Graham Bloice (May 21)
- Re: Troubles with ASN generated code Guy Harris (May 19)