[Wireshark-dev] wmem allocator and GLIB version

2012-10-24 Thread Pascal Quantin
Hi all, wmem_glib_free_all() makes use of g_slist_free_full that was introduced in GLIB 2.28 while our minimum requirement is GLIB 2.14.0. Could we manually free list elements containing dynamically-allocated memory and call g_slist_free() instead to keep compatibility with older GLIB versions?

Re: [Wireshark-dev] RFD: The Future of Memory Management in Wireshark

2012-10-24 Thread Evan Huus
On Wed, Oct 24, 2012 at 8:10 AM, Sébastien Tandel sebastien.tan...@gmail.com wrote: On Wed, Oct 24, 2012 at 1:10 AM, Guy Harris g...@alum.mit.edu wrote: On Oct 18, 2012, at 6:01 PM, Evan Huus eapa...@gmail.com wrote: I have linked a tarball [2] containing the following files: -

Re: [Wireshark-dev] wmem allocator and GLIB version

2012-10-24 Thread Evan Huus
On Wed, Oct 24, 2012 at 8:08 AM, Pascal Quantin pascal.quan...@gmail.com wrote: Hi all, wmem_glib_free_all() makes use of g_slist_free_full that was introduced in GLIB 2.28 while our minimum requirement is GLIB 2.14.0. Could we manually free list elements containing dynamically-allocated

[Wireshark-dev] Direction definition on packet bus with no direction info in packet header

2012-10-24 Thread Andrew Lonsdale
Hi Folks, I'm writing a dissector for an interface which doesn't indicate direction of data flow in the packet headers. I currently capture separate files in pcapng format for uplink and downlink (separate streams), but I could merge the two into a file. Currently I just open one file and merge

[Wireshark-dev] Asterisk AMI and FreeSWITCH ESL dissectors

2012-10-24 Thread Kristian Kielhofner
Hello everyone, Has anyone investigated developing Asterisk AMI and FreeSWITCH ESL Wireshark dissectors? They're both fairly simple protocols and the current telnet dissector *kind of* works but I need TCP reassembly to work properly for both. It seems like Wireshark dissectors would be very