The Buildbot has detected a new failure of Ubuntu-9.10-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Ubuntu-9.10-x64/builds/39
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: ubuntu-9.10-x64
Build
Hi all,
since I updated my trunk tree to revision 31528, I cannot compile
Wireshark on my Windows box (WinXP, MSVC2008SP1, cygwin 1.7.1). I get
the following error:
C:\wireshark\trunknmake -f Makefile.nmake all
Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
Copyright (C)
Pascal Quantin wrote:
Hi all,
since I updated my trunk tree to revision 31528, I cannot compile
Wireshark on my Windows box (WinXP, MSVC2008SP1, cygwin 1.7.1). I get
the following error:
C:\wireshark\trunknmake -f Makefile.nmake all
Microsoft (R) Program Maintenance Utility Version
Hi Gerald,
Le 15/01/2010 21:12, Gerald Combs a écrit :
Pascal Quantin wrote:
Hi all,
since I updated my trunk tree to revision 31528, I cannot compile
Wireshark on my Windows box (WinXP, MSVC2008SP1, cygwin 1.7.1). I get
the following error:
C:\wireshark\trunknmake -f Makefile.nmake
Pascal Quantin wrote:
Hi Gerald,
Le 15/01/2010 21:12, Gerald Combs a écrit :
Pascal Quantin wrote:
Hi all,
since I updated my trunk tree to revision 31528, I cannot compile
Wireshark on my Windows box (WinXP, MSVC2008SP1, cygwin 1.7.1). I get
the following error:
I'll see what I can do to fix this (since I originally did the hack
about -igncr when invokig the bash shell) ...
I've committed an (ugly) hack in SVN #31538 which fixes the problem for
win-setup.sh.
(Although not currently a problem for the Wireshark Windows build, the
real issue is
Gerald Combs wrote:
Would setting win-setup.sh's svn:eol-style to LF help?
I thought about that:
That solution works as long as someone doesn't edit the file locally and
somehow convert the line-endings to dos-style; (I guess this may be a
bit far-fetched).
My (slight) preference: keep the
On Jan 14, 2010, at 12:51 PM, Ing. Rodrigo Castro wrote:
Hi all. I am getting the following error:
Error while capturing packets: read error: PacketReceivePacket failed
Please report this to the Wireshark developers.
(This is not a crash; please do not report it as such.)
That's an
Why the please report this to the wireshark developers message then?
On 16/01/2010, at 8:59 AM, Guy Harris g...@alum.mit.edu wrote:
On Jan 14, 2010, at 12:51 PM, Ing. Rodrigo Castro wrote:
Hi all. I am getting the following error:
Error while capturing packets: read error:
On Jan 15, 2010, at 2:23 PM, Ian Schorr wrote:
Why the please report this to the wireshark developers message then?
Because that message is a generic message for capture errors. The code could
perhaps check for some strings in the error, such as anything with Packet in
it, and suggest
Well, it can mean everything...
- can you reproduce it consistently?
- did it happen after capturing hours and hours?
- if it's a USB network adapter, did you disconnect it?
- did it happen after getting your PC out of hibernation?
GV
--
From:
Hi,
This is my first time to submit a patch here. I'm not sure how long it
usually takes to get some review.
How should I expect when someone may pull this in?
Many thanks,
Joshua
On Wed, Dec 2, 2009 at 12:13 PM, Jeff Morriss jeff.morriss...@gmail.com wrote:
Joshua (Shiwei) Zhao wrote:
Hi
On Jan 15, 2010, at 1:50 PM, Kaul wrote:
Hi,
I'm trying to write a new dissector, and failing miserably getting my tree to
show, because the tree I'm getting in my dissect_PROTONAME() is always NULL,
not sure why.
Null even if you click on the packet?
I'm dissecting over TCP, with
13 matches
Mail list logo
