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

2012-10-28 Thread Evan Huus
On Sat, Oct 27, 2012 at 3:09 PM, Evan Huus eapa...@gmail.com wrote: On Sat, Oct 27, 2012 at 2:17 PM, Dirk Jagdmann d...@cubic.org wrote: General thoughts from the list on whether or not this would be a good idea? some general comments on the whole wmem idea: memory allocation is done almost

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

2012-10-28 Thread Guy Harris
On Oct 28, 2012, at 11:22 AM, Martin Kaiser li...@kaiser.cx wrote: The solution we came up with is to have one DLT. The pcap packet data consists of a pseudo-header and the actual bytes that are transfered. The dissector picks up the direction from the pseudo-header. The capturing tool has

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 7922] Buildbot crash output: fuzz-2012-10-27-11126.pcap

2012-10-28 Thread Bill Meier
On 10/28/2012 4:24 PM, bugzilla-dae...@wireshark.org wrote: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7922 Evan Huus eapa...@gmail.com changed: What|Removed |Added

[Wireshark-dev] WinPCap / Windows 8 Support

2012-10-28 Thread Andrew Pennebaker
It's been years since Wireshark recommended a new version of WinPCaphttp://www.winpcap.org/ (it's been v4.1.2 for years). Is this packet capture library still alive? When I run the Windows 8 Upgrade Assistanthttp://windows.microsoft.com/en-US/windows-8/upgrade-to-windows-8, it reports that

[Wireshark-dev] Interface names on Windows

2012-10-28 Thread Graham Bloice
I've been hacking around trying to improve the display of interface names on Windows. Currently there are 3 components displayed in various dialogs and command line responses; the interface guid (\Device\NPF_{C2E403B5-FAD0-479C-96FD-0E44EB22CD74}), the interface description from WinPCap (Intel(R)

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

2012-10-28 Thread Jakub Zawadzki
On Sun, Oct 28, 2012 at 10:12:41AM -0400, Evan Huus wrote: We might be able to fake the proper scoping using thread-local globals if we wrap everything in functions that assert the state of a dissection. Something like: __thread wmem_allocator_t *packet_scope; __thread gboolean

Re: [Wireshark-dev] Interface names on Windows

2012-10-28 Thread Guy Harris
On Oct 28, 2012, at 4:08 PM, Jakub Zawadzki darkjames...@darkjames.pl wrote: if user description: - not set than: format(%s (%s), friendly_name, interface_description) - set: only user descr. Anyway such code should imho go to winpcap. Which code? The code to get the friendly name, or

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

2012-10-28 Thread Evan Huus
On Sun, Oct 28, 2012 at 7:26 PM, Jakub Zawadzki darkjames...@darkjames.pl wrote: On Sun, Oct 28, 2012 at 10:12:41AM -0400, Evan Huus wrote: We might be able to fake the proper scoping using thread-local globals if we wrap everything in functions that assert the state of a dissection. Something