Re: [Wireshark-dev] SCCP reassembly broken for duplicated SCTP messages.

2011-03-23 Thread Sake Blok
On 24 mrt 2011, at 03:15, Jeff Morriss wrote: > > [Finally got back to this again...] > > Anders had sent me a couple of captures that exhibited the problem. I got > those working in rev 36304: it wasn't a problem in the reassembly code but > rather the TCP dissector's desegmentation logic. S

[Wireshark-dev] buildbot failure in Wireshark (development) on Clang-Code-Analysis

2011-03-23 Thread buildbot-no-reply
The Buildbot has detected a new failure of Clang-Code-Analysis on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/41 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: clang-code-analysis

Re: [Wireshark-dev] TCP dissector handling TCP Fast Retransmit

2011-03-23 Thread Jeff Morriss
On 03/07/2011 10:54 AM, Gerald wrote: --- On *Mon, 3/7/11, Jeff Morriss //* wrote: From: Jeff Morriss Subject: Re: [Wireshark-dev] TCP dissector handling TCP Fast Retransmit To: "Developer support list for Wireshark" Date: Monday, March 7, 2011, 10:09 AM Gerald wrote:

Re: [Wireshark-dev] SCCP reassembly broken for duplicated SCTP messages.

2011-03-23 Thread Jeff Morriss
On 03/03/2011 03:39 PM, Jeff Morriss wrote: Jeff Morriss wrote: Sake Blok wrote: On 3 mrt 2011, at 15:00, Anders Broman wrote: SCCP reassembly will add both segments from duplicated packets thus producing garbage in the reassembled packet. An "easy" fix could perhaps bee to add a flag in pinf

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

2011-03-23 Thread buildbot-no-reply
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/1345 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

Re: [Wireshark-dev] Missing file from website

2011-03-23 Thread Gerald Combs
On 3/23/11 8:17 AM, Chris Maynard wrote: > So despite the indication that 0.99.0 is the last known version to work with > Windows ME, it appears that that can't be true based on this information. > Should the user guide be updated to indicate that Ethereal 0.10.14 is likely > the > last version t

Re: [Wireshark-dev] Wireshark -z vs. tshark -z

2011-03-23 Thread Chris Maynard
Chris Maynard writes: > I added a mention about this to the Roadmap page: > http://wiki.wireshark.org/Development/Roadmap under "Completed Tasks". I > assume > the release notes file gets updated by Gerald when the next release is made? Oops. I reverted the Roadmap wiki page and added an entr

Re: [Wireshark-dev] Wireshark -z vs. tshark -z

2011-03-23 Thread Chris Maynard
Sake Blok writes: > > (without thinking it through very much...) I would say to change it and > > mention the change in the release notes. > > And of course in the Usage, manpage, user manual etc > > (and yes... I think it's a joy to make the occasional superfluous remark ;-)) I made the cha

Re: [Wireshark-dev] problem with linking tvbuff functions

2011-03-23 Thread Stephen Fisher
On Wed, Mar 23, 2011 at 06:24:31PM +0200, Yosi Saggi wrote: > tvb_new_composite > tvb_composite_append > tvb_composite_finalize > Why are those functions not in the libwireshark.def file? Functions are added as they are requested. These 3 were added recently to the trunk (SVN) sourcew code by

[Wireshark-dev] problem with linking tvbuff functions

2011-03-23 Thread Yosi Saggi
Hi I have used in my dissector 3 functions from the tvbuff.c code: tvb_new_composite tvb_composite_append tvb_composite_finalize When trying to compile my plugin I get an error: error LNK2019: unresolved external symbol _tvb_composite_finalize referenced in function error LNK2019: unresolve

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-PowerPC

2011-03-23 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/2269 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reas

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

2011-03-23 Thread buildbot-no-reply
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/1338 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

[Wireshark-dev] buildbot failure in Wireshark (development) on Visual-Studio-Code-Analysis

2011-03-23 Thread buildbot-no-reply
The Buildbot has detected a new failure of Visual-Studio-Code-Analysis on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Visual-Studio-Code-Analysis/builds/228 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: vs

Re: [Wireshark-dev] Missing file from website

2011-03-23 Thread Chris Maynard
Gerald Combs writes: > Even Ethereal 0.99.0 may not work: > > http://www.ethereal.com/lists/ethereal-dev/200604/msg00295.html > > We added memory protection and guard pages via VirtualAlloc + > VirtualProtect in 0.99.0. According to MSDN those calls are only > supported on Windows 2000 and la

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

2011-03-23 Thread buildbot-no-reply
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/2616 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.6-x64

2011-03-23 Thread buildbot-no-reply
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/2179 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.6-x64 Build Reason: Bui

Re: [Wireshark-dev] setting up for win32

2011-03-23 Thread Bill Meier
On 3/23/2011 2:01 AM, Roland Knall wrote: Hi Another issue, at least for me, has been the Windows file endings. In the file win-setup.sh, there are several file-endings written with \r\n, which is Windows specific. The cygwin bash can not handle this file with those endings. Open the file with a

Re: [Wireshark-dev] [Wireshark-commits] rev 36286: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-rlc.c

2011-03-23 Thread Martin Mathieson
Oops, that was 1020 & 1021, rather. On Wed, Mar 23, 2011 at 10:58 AM, wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=36286 > > User: martinm > Date: 2011/03/23 03:58 AM > > Log: > Don't assign proto_item pointers that are not used. > > Coverity CIDs 1021 & 1022. > >

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

2011-03-23 Thread buildbot-no-reply
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/1333 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason: