Wireshark mailing list archives
Using tfs.h in a custom dissector
From: "Colin Helliwell" <colin.helliwell () LN-Systems com>
Date: Tue, 31 Jan 2012 18:51:43 -0000
Not sure if I'm missing something, but is it the case that a dissector in 'plugins' can't use the true_false strings provided by tfs.h? When I try (e.g. "..., TFS(&tfs_true_false), ..."), I get compilation errors: packet-is3.c(633) : error C2099: initializer is not a constant packet-is3.c(633) : warning C4047: 'initializing' : 'const void *' differs in levels of indirection from 'int' packet-is3.c(633) : warning C4047: 'initializing' : 'guint32' differs in levels of indirection from 'char [9]' packet-is3.c(633) : warning C4047: 'initializing' : 'int' differs in levels of indirection from 'void *' (I'm building under Windows/nmake, with VS9.0). I also noticed that other dissectors in this directory seem to be declaring their own strings instead of using the 'supplied' ones?
___________________________________________________________________________ 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:
- Using tfs.h in a custom dissector Colin Helliwell (Jan 31)
- Re: Using tfs.h in a custom dissector Anders Broman (Jan 31)