Eloy Paris wrote: > Hi Jeff, > > On 03/11/2010 05:19 PM, Jeff Morriss wrote: > > [...] > >> libwireshark is NOT thread safe. If you're using multiple threads, >> you'd need one lock to prevent more than one thread from entering >> libwireshark simultaneously. > > Indeed. I personally found that out while integrating libwireshark into > netexpect. For one particular feature netexpect needs to dissect two > packet simultaneously (or keep two dissection results in memory at the > same time) so I ended up using a very ugly hack, which I still have had > a chance to fix in a better way. > > Are there any plans, or at least a desire, to make it thread-safe at > some point in the future? Is there any README or wiki page that gives at > least a big picture overview of what such a project would entail? I > understand it's a big undertaking...
Yes, it is big. See: http://wiki.wireshark.org/Development/multithreading for more info. ___________________________________________________________________________ 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-requ...@wireshark.org?subject=unsubscribe
