The Buildbot has detected a new failure of OSX-10.6-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.6-x64/builds/1577
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.6-x64
Build Reason:
Bui
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/788
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-x64
Build Reason:
B
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/2076
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Bui
On Jan 8, 2011, at 10:15 AM, hsivank wrote:
> Hello the Wireshark team,
>
> -A patch to allow drag and drop on wireshark icon doc :
Checked in.
> -A patch to fix configure with cmake with macports libs :
Checked in.
___
S
It's working in 1.5.0-SVN-35425. I found out that there have been problems
with tshark versus Wireshark output vice what the GUI reports even back to
version 1.2.9. I had been using tshark for output and looking at the GUI
with Wireshark and that was consistent in 1.2.9. Consistency was broken
b
Hello the Wireshark team,-A patch to allow drag and drop on wireshark icon doc :
gtkosxapplication_drag_and_drop.diff
Description: Binary data
It does not require old(Carbon) ScriptExec-A patch to fix configure with cmake with macports libs :
cmake_modules_FindGTK2.cmake.diff
Description: Binary
On 8 jan 2011, at 15:12, Douglas Wood wrote:
> I have tried the options that you have stated. It doesn't appear to make
> any difference. For what it's worth, tshark seems to generate the correct
> values for TCP Window Size. PDML output is different for tshark than
> Wireshark.
I just updated
I have tried the options that you have stated. It doesn't appear to make
any difference. For what it's worth, tshark seems to generate the correct
values for TCP Window Size. PDML output is different for tshark than
Wireshark.
Doug
-Original Message-
From: wireshark-dev-boun...@wiresh