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/2644
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Bui
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/2292
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build Reas
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/2207
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.6-x64
Build Reason:
Bui
On Mar 24, 2011, at 3:59 PM, John Sullivan wrote:
> (Aside: my attitude to dead stores is that eliminating them is a job
> for the compiler.
It is, and I think at least some (perhaps all) modern compilers will do that
already. However, a dead store could either be "this is part of an idiom, an
On Mar 24, 2011, at 1:57 PM, Chris Maynard wrote:
> Or ... convert the dissector to a "new-style" dissector where the number of
> bytes it consumes is returned,
...as long as the dissector cannot validly dissect an empty payload (e.g., an
empty reply in a protocol where the request/response mat
> (Aside: my attitude to dead stores is that eliminating them is a job
> for the compiler. The programmer's job is not to micro-optimize things
> that can be done better by machine, but to structure the code so as to
> make the semantics as clear as possible. And I think that includes, as
> already
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/250
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: vs
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/1360
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-x64
Build Reason:
On Thursday, March 24, 2011, 8:57:42 PM, Chris Maynard wrote:
> Alexis La Goutte writes:
>> What it the official solution to fix this ?
>> 1) Remove the code
>> 2) Ignore this warning
>> 3) Comment the code add a
>> /* offset += 1; Remove Clang Dead increment */
> Or ... convert the di
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/2288
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build Reas
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/2638
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Bui
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/2201
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-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/2468
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason
Chris Maynard wrote:
Alexis La Goutte writes:
What it the official solution to fix this ?
1) Remove the code
2) Ignore this warning
3) Comment the code add a
/* offset += 1; Remove Clang Dead increment */
Or ... convert the dissector to a "new-style" dissector where the number of
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/2636
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Bui
Alexis La Goutte writes:
> What it the official solution to fix this ?
> 1) Remove the code
> 2) Ignore this warning
> 3) Comment the code add a
> /* offset += 1; Remove Clang Dead increment */
Or ... convert the dissector to a "new-style" dissector where the number of
bytes it consume
> What it the official solution to fix this ?
> 1) Remove the code
> 2) Ignore this warning
> 3) Comment the code add a
> /* offset += 1; Remove Clang Dead increment */
I would say configure clang to not emit this warning. This idiom of adding a
proto_item and then incrementing the offset i
On Thu, Mar 24, 2011 at 08:56:26PM +0100, Alexis La Goutte wrote:
> And there is a lot of Dead increment
> What it the official solution to fix this ?
> 1) Remove the code
> 2) Ignore this warning
> 3) Comment the code add a
> /* offset += 1; Remove Clang Dead increment */
I would say #1
Hi,
I take a look in Clang Analysis report (
http://www.wireshark.org/download/automated/analysis/ ).
And there is a lot of Dead increment
Example : in the packet-ieee80211.c
6390case TAG_POWER_CONSTRAINT: /* 7.3.2.15 Power Constraint element (32)
*/
6391{
6392 if (tag_len != 1)
6
Sake Blok writes:
> That's great, could you update the wiki page on Loopback interfaces an update
with your findings too?
I had added a reference to proxocket already, but I just expanded it to include
my experience with it.
__
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/2464
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason
On 24 mrt 2011, at 17:40, Chris Maynard wrote:
> While certainly not as good/easy as capturing loopback traffic on a *NIX
> platform, so far this has been by far the best way for me to obtain loopback
> traffic on Windows. Maybe others will find this tool useful as well.
That's great, could you
As probably most of you know, it's not possible to capture loopback traffic on
Windows ... or is it?
The Wireshark Loopback wiki page provides some information and potential
work-arounds for this problem, such as installing the "Microsoft Loopback
Adapter", but it also indicates that "... in most
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/2632
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
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/1351
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-x64
Build Reason:
Hello
The dissectory has now been fuzz-tested as well, with nearly 250 MB
worth of various capture files. It passed.
The updated version of the patch is online.
kind regards,
Roland
___
Sent via:Wireshark-dev mailing lis
26 matches
Mail list logo
