Wireshark · Wireshark-dev: Re: [Wireshark-dev] Using tfs.h in a custom dissector

[Anders Broman <a.broman@xxxxxxxxxxxx>]

Colin Helliwell skrev 2012-01-31 19:51:

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?

 

You can't export data between .dll:s so it's a limitation for plugins.
Regards
Anders

 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe