2007/3/30, Jeff Morriss [EMAIL PROTECTED]:
Peter Johansson wrote:
I compiled Wireshark with HAVE_AIRPDCAP by mistake (since I do not
have AirPcap). This leads to a runtime problem however. When
choosing options from the Capture interfaces dialog, I receive a
modal dialogue
Hi,
Applying a filter in the current build results in:
13:13:01 Err Per-packet memory corrupted.
Press any key to exit
Best regards
Anders
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
Hi,
I modified dfilter-macro for a strict aliasing gcc warning which
stopped the compilation when using -Werror. I replaced (void**) by (void*)
I had no problem on my debian but it seems you do. Sorry. Can you tell
me on which platform and compiler it occured?
I reverted back these fixes on
Hi,
Hmm the problem seems to actually be in the H.263 dissector...
Best regards
Anders
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sebastien
Tandel
Sent: den 30 mars 2007 14:08
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev]
Hi all,
nmake -f Makefile.nmake setup is not working for me.
All the steps prio to this are correct as I hv verified it
through verify_tools option.
wget is not working for me.
Ah, I guess that explains it. Red Hat Enterprise Linux 3 is equipped
with gtk2-2.2.4-19 (and gtk+-1.2.10-31). Is gtk 2.4 or higher a
requirement for building a Wireshark rpm? I did not see any mention of
any minimum 2.x requirement in the README.developer, README.linux or any
other README*
You probably need to setup wget to see through your proxy.
You can find your proxy details in your browsers connections settings.
You set the proxy for wget under cygwin by adding a file into your
cygwin ~ directory, which maps to c:\Documents and Settings\username
The file is called .wgetrc and
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows Server
2003 R2\Bin and not the directory mentioned in the developper's guide (Visual
studio dir). Is it normal ?
Developper's guide :
Checking for required applications:
cl: /cygdrive/c/Program Files/Microsoft Visual
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows Server
2003 R2\Bin and not the directory mentioned in the developper's guide (Visual
studio dir). Is it normal ?
The paths shown in the dev guide are for information only and refer to a
VC 6.0
So someone has already built Wireshark 0.99.5 under Windows 2000 ?
Why tshark and other bin do not work ?
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de Graham Bloice
Envoyé : vendredi 30 mars 2007 17:03
À : Developer support list for Wireshark
Objet :
CANDIA, Fabrice wrote:
So someone has already built Wireshark 0.99.5 under Windows 2000 ?
Why tshark and other bin do not work ?
I think you're confusing the version of VC and the OS. I build it using
VC 6.0 on XP, the same as the buildbot and have previously built on W2K,
but not for a
In an attempt to circumvent this problem I tried to disable gtk2.
Unfortunately, it doesn't seem to work. I still get the same undefined
reference as before. But if 'gtk_text_buffer_select_range' is
applicable for 2.4+ only and I've disabled gtk2, then why is it still
trying to call it?
Graham Bloice wrote:
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows Server
2003 R2\Bin and not the directory mentioned in the developper's guide
(Visual studio dir). Is it normal ?
The paths shown in the dev guide are for information
Hi,
I'm writing my first protocol dissector (a plugin).
I have the basics up and running. However,
this protocol has a couple of unique issues:
1 Although encapsulated in UDP, it doesn't use a
well-known port. I'm OK with telling wireshark
to decode using the protocol specifically
On 3/30/07, Maynard, Chris [EMAIL PROTECTED] wrote:
In an attempt to circumvent this problem I tried to disable gtk2.
Unfortunately, it doesn't seem to work. I still get the same undefined
reference as before. But if 'gtk_text_buffer_select_range' is
applicable for 2.4+ only and I've
On Fri, Mar 30, 2007 at 08:23:08PM +0200, Ulf Lamping wrote:
You may try GTK 1.2 which should still work. Don't ask me how to do
(configure) this, I'm currently Win32 only ;-)
./configure --disable-gtk2 :)
Steve
___
Wireshark-dev mailing list
On Fri, Mar 30, 2007 at 02:47:50PM -0700, Stephen Fisher wrote:
Yes, but the problem with using Decode As is that it assigns that
port to your protocol bi-directionally. The dissector then can't tell
the difference in the sender and receiver. Also the Decode As
settings aren't saved
On Thu, Mar 29, 2007 at 03:28:09AM +0200, Ulf Lamping wrote:
Just stumbled over Gtk+ for Mac OS X:
http://developer.imendio.com/projects/gtk-macosx
which is a native port of GTK+ - so you won't need an X server. The
screenshots suggests to be aimed towards bringing a native The Gimp
to
18 matches
Mail list logo
