[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/613 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason: B

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/1731 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

[Wireshark-dev] Diameter tech discussion group

Dear all, I wanted to let you know on technical Diameter discussion group on LinkedIn http://www.linkedin.com/groups?mostPopular= &gid=1787697 I believe you will find the Diameter related discussions there of interest. Best

Re: [Wireshark-dev] Automatic test for a dissector DLL

The way I do this is to modify the printpdml code. I had similar requirements to "flatten" the hierarchy to create something more amenable to statistical analysis. Dealing with PDML output that reaches 10 gigabytes of XML, all in one XML document, requires writing incredibly weird XML processi

Re: [Wireshark-dev] Automatic test for a dissector DLL

Hi, One way or the other you'll have to script it. Take the tshark -V output, pull it through awk/sed/perl/ to see where your protocol output starts (check lines starting at start-of-line for your protocol name) and go from there (until empty line). Thanks, Jaap On Tue, 14 Dec 2010 06:11:39 +01