Hi,
README.win32 has is for Win32, so I would guess README.bsd
Thanx,
Jaap
On Wed, 2 Aug 2006, Stephen Fisher wrote:
> On Wed, Jul 26, 2006 at 12:43:38PM -0600, John McDermott wrote:
>
> > Can you please post the appropriate changes to README.bsd to describe
> > what you did so other users can
On Wed, Jul 26, 2006 at 12:43:38PM -0600, John McDermott wrote:
> Can you please post the appropriate changes to README.bsd to describe
> what you did so other users can try that, too?
I am writing down all of the packages that are needed to compile
Wireshark on OpenBSD. Is there already a lis
Checked in.
Brg
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Richard van der Hoff
Skickat: den 26 juli 2006 15:33
Till: Developer support list for Wireshark
Ämne: [Wireshark-dev] clopts test fix
An error message has been changed, such that the com
Checked in.
Brg
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Richard van der Hoff
Skickat: den 26 juli 2006 15:29
Till: Developer support list for Wireshark
Ämne: [Wireshark-dev] [patch] capture_sync.c cosmetics
This patch fixes a couple of commen
Checked in.
Brg
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Peter Johansson
Skickat: den 31 juli 2006 17:51
Till: wireshark-dev@wireshark.org
Ämne: [Wireshark-dev] Patch to conversation.c
Hi,
the supplied patch fixes a problem where the options
Hi,
The head of the stack just before the exception is given below.
The actual error is in proto_tree_set_representation at the call:
g_vsnprintf(fi->rep->representation, ITEM_LABEL_LENGTH, format, ap);
The format has a single %I64x value needed.
The entry to the routine throws an MSVC
Hello,
On Linux, I can't reproduce the crash mentioned in
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1025
Can someone please try to test this on Windows and maybe provide a stack
trace?
Thanks
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are
