buildbot | 2 Jan 2011 09:28
Favicon

buildbot failure in Wireshark (development) on Ubuntu-10.04-x64

The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark (development).
Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/906

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: ubuntu-10.04-x64

Build Reason: 
Build Source Stamp: 35323
Blamelist: krj

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 2 Jan 2011 09:30
Favicon

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

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/2002

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: osx-10.5-x86

Build Reason: 
Build Source Stamp: 35323
Blamelist: krj

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 2 Jan 2011 09:31
Favicon

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/723

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: windows-7-x64

Build Reason: 
Build Source Stamp: 35323
Blamelist: krj

BUILD FAILED: failed nmake all

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 2 Jan 2011 09:34
Favicon

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/1843

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: windows-xp-x86

Build Reason: 
Build Source Stamp: 35323
Blamelist: krj

BUILD FAILED: failed nmake all

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 2 Jan 2011 09:40
Favicon

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

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/1717

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: osx-10.5-ppc

Build Reason: 
Build Source Stamp: 35323
Blamelist: krj

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 2 Jan 2011 09:55
Favicon

buildbot failure in Wireshark (development) on Solaris-10-SPARC

The Buildbot has detected a new failure of Solaris-10-SPARC on Wireshark (development).
Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/Solaris-10-SPARC/builds/1401

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: solaris-10-sparc

Build Reason: 
Build Source Stamp: 35323
Blamelist: krj

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

Douglas Wood | 2 Jan 2011 16:31
Picon

Question about tcp window scaling value

In Wireshark 1.4.2, export to PDML from tshark sometimes results in a different value for tcp window size
compared to doing the same export from the Wireshark GUI.  The different value reflects multiplying the
tcp window value with the current window scaling size for tshark and not taking window scaling into
account for Wireshark.

Is this a bug?  If not, how can I tell the difference between the two outputs?  I'd rather not write code that
cares if tshark generated the output or Wireshark.

Sent from my iPad
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

Ed Beroset | 2 Jan 2011 17:07
Picon

Re: Question about tcp window scaling value

Douglas Wood wrote:
> In Wireshark 1.4.2, export to PDML from tshark sometimes results in a different value for tcp window size
compared to doing the same export from the Wireshark GUI.  The different value reflects multiplying the
tcp window value with the current window scaling size for tshark and not taking window scaling into
account for Wireshark.
> 
> Is this a bug?  

No, it's a feature.  :)

If not, how can I tell the difference between the two outputs?  I'd 
rather not write code that cares if tshark generated the output or 
Wireshark.

There is a TCP preference "Window scaling" that controls this.  Note 
that you must also have the "Analyze TCP sequence numbers" enabled for 
this to take effect.

As always, you can also specify an option override on the command line 
as -o tcp.window.scaling:TRUE

Ed
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

news.gmane.com | 3 Jan 2011 09:50
Picon

Re: [Wireshark-commits] rev 35253: /trunk/ /trunk/doc/: README.developer /trunk/epan/: tvbuff.c tvbuff.h


"Stephen Fisher" <steve@...>
wrote in message news:20101223181634.GA30749@...
> I've introduced a new function called tvb_get_ephemeral_unicode_string()
> for converting UTF-16 strings in a tvbuff to UTF-8 for display in
> Wireshark.  This new function even works with tshark (at least on Unix)
> if using a UTF-8 compatiable terminal emulator:

Does this replaces tvb_get_ephemeral_faked_unicode?
The function name suggests, that the return value must be released. Is there
also a function returning a string that will be garbage collected?

--
Andy

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

Guy Harris | 3 Jan 2011 11:08
Picon
Favicon

Re: [Wireshark-commits] rev 35253: /trunk/ /trunk/doc/: README.developer /trunk/epan/: tvbuff.c tvbuff.h


On Jan 3, 2011, at 12:50 AM, news.gmane.com wrote:

> "Stephen Fisher" <steve@...>
> wrote in message news:20101223181634.GA30749@...
>> I've introduced a new function called tvb_get_ephemeral_unicode_string()
>> for converting UTF-16 strings in a tvbuff to UTF-8 for display in
>> Wireshark.  This new function even works with tshark (at least on Unix)
>> if using a UTF-8 compatiable terminal emulator:
> 
> Does this replaces tvb_get_ephemeral_faked_unicode?
> The function name suggests, that the return value must be released.

Within the context of Wireshark, no, it doesn't; it suggests, due to the "ephemeral" in the name, that it's
automatically released when dissection is started on a new packet, although, given that most routines
that return ephemerally-allocated memory have just "ep_" at the beginning the name, it should perhaps be
named "ep_tvb_get_unicode_string()" or something such as that to make it clearer.  (Yes,
tvb_get_ephemeral_faked_unicode() had "ephemeral", not "ep", in its name, but that was arguably an
error as well.  "ep_" should come before "tvb_", as other ephemeral-allocation routines have names that
begin with "ep_", including "ep_tvb_memdup()".)

> Is there
> also a function returning a string that will be garbage collected?

No - Wireshark doesn't do garbage collection (unless one or more of the extension languages does, and then
it does it only for items allocated in the environment for the extension languages in question, courtesy
of the language's garbage collector).  It just does "ephemeral" and "session" allocation, where all
items allocated with a particular lifetime are automatically released in bulk.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
(Continue reading)


Gmane