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/2604
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-x64
Build Reason:
On Aug 1, 2011, at 11:41 PM, Guy Harris wrote:
On Aug 1, 2011, at 1:51 PM, Anders Broman wrote:
so I assume these are shown for 802.11 interfaces.
...which, on Windows, means AirPcap interfaces.
I'll fire up my Windows XP virtual machine and see where the VU meter:
Hi,
@Michael
Ref http://mail.gnome.org/archives/commits-list/2010-June/msg00397.html
Could you try to move
# define gtk_widget_get_realized(x) GTK_WIDGET_REALIZED(x)
To GTK 2.18 ?
Regards
Anders
-Original Message-
From: wireshark-dev-boun...@wireshark.org
Hello,
I have currently several instances of Wireshark running. Each instance captures
with a specific capture filter. I forget which windows shows the (live) capture
with which capture filter. So I don't know if packets are missing (lost on
wire) or suppressed by filter.
It would be nice to
On Thu, Aug 4, 2011 at 1:56 PM, Helge Kruse helge.kruse-nos...@gmx.net wrote:
It would be nice to have a possibility to display the capture filter (as
entered in dialog) while the capture is running.
The capture filter is displayed in the title bar like this: Capturing
from en0 (tcp or udp) in
All-
I have developed a suite of plugins, several of which deal with packet
decryption. Decrypting the packets (in-house protocol) requires tracing each
packet to determine packet counts and watching key exchanges.
We are currently attempting to work with some extremely large trace files,
On Aug 4, 2011, at 1:30 PM, Anders Broman wrote:
Hi,
@Michael
Ref http://mail.gnome.org/archives/commits-list/2010-June/msg00397.html
Could you try to move
# define gtk_widget_get_realized(x) GTK_WIDGET_REALIZED(x)
To GTK 2.18 ?
I tried. gtk_widget_get_realized() doesn't seem to be
On Wed, Aug 03, 2011 at 09:36:40PM -0400, Maynard, Chris wrote:
On Tue, Aug 02, 2011 at 11:22:03AM -0400, Jeff Morriss wrote:
Do we already require Python to build Wireshark [even from a source
distribution]?
I don't think so.
Isn't it?
===C:\Python27\python.exe:
What is the rationale behind this change? I normally change the decode
as for only the source or destination port as needed, although perhaps
both would work fine in my case as well.
If it's kept this way, listing the source and destination ports next to
both would be very helpful - I use the
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Stephen Fisher
Sent: den 4 augusti 2011 17:27
To: wireshark-dev@wireshark.org
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 38333: /trunk/gtk/
/trunk/gtk/:
On Thu, Aug 04, 2011 at 05:36:59PM +0200, Anders Broman wrote:
Well I most frequently chose Both and got tired of having to change
it all the time. If most people Want it as it was I'm not oposed to
change it back.
That's a good enough reason for me :). I can't think of any reason why
it
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Stephen Fisher
Sent: den 4 augusti 2011 17:50
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 38333: /trunk/gtk/
Hi bros,
After building release 1.6.1 successful, I run ./wireshark (not install)
And it presents:
/*ERROR:packet.c:1531:heur_dissector_add: assertion failed:
(sub_dissectors != NULL)
Aborted (core dumped)*/
It is ok if I run make install before.
Please help me how to run ./wireshark without
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/2609
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-x64
Build Reason:
Am 04.08.2011 14:09, schrieb Stig Bjørlykke:
The capture filter is displayed in the title bar like this: Capturing
from en0 (tcp or udp) in recent versions of Wireshark.
Ah, I see!.
Probably one more reason to upgrade Wireshark in out company.
Unfortunately this requires the generation of a
There should be a file called core in the directory you called Wireshark
from. Please send this file.
Regards
Roland
Am 04.08.2011 um 18:25 schrieb Ngo Hoang Thang ngohoangth...@gmail.com:
Hi bros,
After building release 1.6.1 successful, I run ./wireshark (not install)
And it presents:
On Aug 4, 2011, at 10:47 AM, Roland Knall wrote:
There should be a file called core in the directory you called Wireshark
from. Please send this file.
More precisely, please send this file, and the entire build directory for
Wireshark, to somebody also running the same version of Fedora.
An exception in packet.c can be nearly anything. The backtrace is what
I am looking for, as it would tell which dissector caused the
underlying issue.
Roland
Am 04.08.2011 um 21:23 schrieb Guy Harris g...@alum.mit.edu:
On Aug 4, 2011, at 10:47 AM, Roland Knall wrote:
There should be a
On Aug 4, 2011, at 12:25 PM, Roland Knall wrote:
An exception in packet.c can be nearly anything. The backtrace is what
I am looking for,
Yes, as I said. My point is that sending us the core dump won't necessarily
make it possible for us to get a backtrace; getting the backtrace on the
On Aug 2, 2011, at 2:33 PM, Guy Harris wrote:
On Aug 2, 2011, at 2:25 PM, Stig Bjørlykke wrote:
Are you sure? Isn't this for (some) regular wireless adapters on Windows?
I'm not getting any information from my AirPcap...
WinPcap doesn't support NDIS 6.0, so it doesn't support the
On Thu, Aug 04, 2011 at 08:20:55PM +, cmayn...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38340
User: cmaynard
Date: 2011/08/04 01:20 PM
Log:
Don't report svn version if not building from svn. Change prompted by
Anders Broman wrote:
Michael Tüxen skrev 2011-08-01 18:39:
On Aug 1, 2011, at 6:14 PM, Anders Broman wrote:
Hi,
I found this code in a more recent version of the file
http://buzztard.svn.sourceforge.net/viewvc/buzztard/trunk/buzztard/src/ui/edit/gtkvumeter.c?view=log
#if
Joerg Mayer wrote:
On Thu, Aug 04, 2011 at 08:20:55PM +, cmayn...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38340
User: cmaynard
Date: 2011/08/04 01:20 PM
Log:
Don't report svn version if not building from svn. Change prompted by
Stephen Fisher wrote:
On Wed, Aug 03, 2011 at 09:36:40PM -0400, Maynard, Chris wrote:
On Tue, Aug 02, 2011 at 11:22:03AM -0400, Jeff Morriss wrote:
Do we already require Python to build Wireshark [even from a source
distribution]?
I don't think so.
Isn't it?
===
On Aug 3, 2011, at 2:39 AM, sagar Guledagudda wrote:
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of sagar Guledagudda
Sent: den 3 augusti 2011 10:53
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] wireshark on 64
On Thu, Aug 04, 2011 at 06:33:34PM -0400, Jeff Morriss wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38340
User: cmaynard
Don't report svn version if not building from svn. Change prompted by
Isn't Python also necessary for the Wireshark Python API? (It's disabled by
default, unlike the Lua API.)
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:
On Fri, Aug 05, 2011 at 12:25:08AM +, ger...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38345
User: gerald
Date: 2011/08/04 05:25 PM
Log:
Use GLIB2_LDFLAGS instead of GLIB2_LIBRARIES for wsutil, since it
includes the path to the libraries.
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/1975
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: ubuntu-10.04-x64
Build
On 08/04/2011 07:35 PM, Tony Trinh wrote:
Isn't Python also necessary for the Wireshark Python API? (It's disabled
by default, unlike the Lua API.)
Yes, but here we're talking about whether we have/should have a (hard)
requirement to have Python in order to compile Wireshark (from the
source
30 matches
Mail list logo
