[Moving this to the dev list...]
Richard van der Hoff wrote:
Has wireshark stopped supporting capture from a fifo recently?
I'm sure I used to be able to do things like the following:
$ mkfifo fifo
$ (cat cap; sleep 5; cat cap) fifo
$ tshark -i fifo
But it now dies after the first
Richard van der Hoff wrote:
[tshark from a fifo]
Ulf - I notice you made the relevant change here (r16787) - is there any
reason why tshark shouldn't use capture_loop_dispatch to do its
processing, rather than attempting to use cap_pipe_dispatch or
pcap_dispatch directly?
well, there
This patch fixes a couple of comments in capture_sync.c.
--
Richard van der Hoff [EMAIL PROTECTED]
Telephony Gateways Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
Index: capture_sync.c
===
--- capture_sync.c
An error message has been changed, such that the commandline options
test doesn't work any more.
This patch fixes the test accordingly.
--
Richard van der Hoff [EMAIL PROTECTED]
Telephony Gateways Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
Index: test/suite-clopts.sh
Richard van der Hoff wrote:
Richard van der Hoff wrote:
[tshark from a fifo]
Ulf - I notice you made the relevant change here (r16787) - is there
any reason why tshark shouldn't use capture_loop_dispatch to do its
processing, rather than attempting to use cap_pipe_dispatch or
Hey all,
Using the install-deps build target fixed the problem. It works
like a charm (well... it loads the plugin). Now the only problems that
I have are ones with my code. And I can deal with my code. Thanks so
much!
-Steve
-Original Message-
From: [EMAIL PROTECTED]
The fact that you have to do an install-dep isn't documented anywhere...
It might not be a bad thing to add to readme.win32.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter
Johansson
Sent: Wednesday, July 26, 2006 6:19 AM
To: Developer support
Hi,
You could write something up and post a patch.
You may also consider an addition in the developer guide, very usefull for
Win32 development.
Thanx,
Jaap
On Wed, 26 Jul 2006, Steve Grinwis wrote:
The fact that you have to do an install-dep isn't documented anywhere...
It might not be a
Martin Mathieson wrote:
name [A-Za-z][-a-z0-9_]*[-a-zA-Z0-9_]*
Wouldn't
[A-Za-z][-a-zA-Z0-9_]*
suffice? ([...]* matches zero or more occurrences, and [-a-zA-Z0-9_] is
a superset of [a-z0-9_].)
___
Wireshark-dev mailing list
One have to remember though to run nmake with the install-deps build
target after every recompilation of the source (for any change you
make). Otherwise Wireshark is started with the old compiled code. I
can't remember the amount of times I have been trying to debug my code
and it just does
Steve,
Can you please post the appropriate changes to README.bsd to describe what
you did so other users can try that, too?
Thanks,
--john
On Wed, 26 Jul 2006 03:11:06 -0600, [EMAIL PROTECTED]
wrote:
On Tue, Jul 25, 2006 at 08:40:38AM -0700, Stephen Fisher wrote:
On Mon, Jul 24, 2006 at
I'm going to work up a path to the readme.win32 to include this
information. I think it would be a good idea to include standard build
instructions something like this:
To get a standard build working:
To start setup and download all the required packages:
Nmake -f Makefile.nmake setup
To
You may want to include: nmake -fmakefile.nmake distclean
as the first step. This will get rid of auto generated files that may
cause initial Win32 build to fail.
-Tim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Grinwis
Sent: Wednesday,
Hello,
anyone who knows his way around Wiresharks exception code (or C's
setlongjmp
etc statements). If so, please have a look at bug 1001.
thanks
Joerg
On Wed, Jul 26, 2006 at 01:55:11PM +, [EMAIL PROTECTED] wrote:
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1001
---
If you could send a capture showing the problem to the list (or directly to
me if you'd prefer), I'll take a look.
Martin
- Original Message -
From: Keith French [EMAIL PROTECTED]
To: Developer support list for Wireshark wireshark-dev@wireshark.org
Sent: 25 July 2006 21:48
Subject: Re:
Martin Mathieson wrote:
name [A-Za-z][-a-z0-9_]*[-a-zA-Z0-9_]*
Wouldn't
[A-Za-z][-a-zA-Z0-9_]*
suffice? ([...]* matches zero or more occurrences, and [-a-zA-Z0-9_] is
a superset of [a-z0-9_].)
That would have been the obvious fix to make in the first place, I was
lazily
Ok. Please find attached my patch for readme.win32. It should
hopefully be a good starting point for people trying to build Wireshark
on windows for the first time.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cook, Timothy
Sent: Wednesday, July
Small error. The failure comes when I try
to do:
gtk_widget_show (window);
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Steve Grinwis
Sent: Wednesday, July 26, 2006
3:57 PM
To: Developer
support list for Wireshark
Subject: [Wireshark-dev] GTK+
issues
Steve Grinwis wrote:
Hey all.
I’ve come across a new problem that I’m having trouble with. I need my
plug-in to be able bring up a pop-up screen so that I can get the user
to enter some information. I had it working using the windoze API and
it was working fine, however, obviously it’s
The data I am gathering is an encryption key. It's going to
change potentially on a packet by packet basis. With the wrong key,
decryption failure will occur and no useful level of dissection will
take place. Therefore I get the user to enter an encryption key as part
of the dissector
Hi,
Le mercredi 26 juillet 2006 à 21:54 +0200, Joerg Mayer a écrit :
Hello,
anyone who knows his way around Wiresharks exception code (or C's
setlongjmp
etc statements). If so, please have a look at bug 1001.
It looks like free(0) isn't valid with their setup.
From the code it doesn't
On 7/26/06, Martin Mathieson [EMAIL PROTECTED] wrote:
Martin Mathieson wrote:
name [A-Za-z][-a-z0-9_]*[-a-zA-Z0-9_]*
Wouldn't
[A-Za-z][-a-zA-Z0-9_]*
suffice? ([...]* matches zero or more occurrences, and [-a-zA-Z0-9_] is
a superset of [a-z0-9_].)
That would have
22 matches
Mail list logo
