Hi list,
Looking at bug 3489 (which need to be solved in 1.0.9) and the history of the
Copy as Filter feature, with complaints on memory usage, I wonder if we need
to make this an optional feature. Optional in that it can be selected in the
user preferences if this features is to be available,
Hi Jaap ( list),
As the father of the copy as filter functionality, I would vote for it
to be present all the time in the packet details pane (where I use it most).
Keeping track of all possible filters for the packet list pane seems like an
overkill to me and could be made optional to save
Hi,
I've been playing around with the 'merge and compare' feature in the latest
development build.
I've used it to try and compare duplicate streams sent to two different
multicast addresses.
The results show a number of 'lost packets', but I am very sure the packets
reported as 'lost'
Hi,
Do you use the same naming scheme in the Python bindings as we use in
Lua?
I think we should have the same names for equal functionality in both
Python and Lua.
--
Stig Bjørlykke
___
Sent via:Wireshark-dev
hi,
Can you help me
I don't be able to build wireshark.exe for win32.
I have used developer-guide to compile the source.
The steps before nmake -f Makefile.nmake all it'ok
When i start nmake -f Makefile.nmake all all seem to go well but when
start link i have this error
Linking
Hi,
It may be a problem with your path, cygwin link chosen before MS studio.
Regards
Anders
_
Från: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] För Leonardo
Skickat: den 31 maj 2009 20:44
Till: wireshark-dev@wireshark.org
Ämne: [Wireshark-dev]
On May 31, 2009, at 12:14 PM, Anders Broman wrote:
It may be a problem with your path, cygwin link chosen before MS
studio.
I doubt it's getting the wrong version of link; it appears to be
running Microsoft's link:
link @C:\DOCUME~1\leomik\IMPOST~1\Temp\nm116.tmp
Microsoft (R)
Thanks Mike. I'll try installing the SDK if I ever need to compile with
VS6 again. For now, I'm just going to stick with VS2008EE for 1.2+. Up
'til now I have only been building Windows installers against the 1.0.x
tree, not 1.1.x and the SDK wasn't required for those.
As for the compiler
etx...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=28551
User: etxrab
Date: 2009/05/31 12:55 PM
Log:
Copy the changes from:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=28534
User: wmeier
Date: 2009/05/30 11:07 AM
On Sat, May 30, 2009 at 19:36, Guy Harris g...@alum.mit.edu wrote:
On May 30, 2009, at 2:31 PM, Sébastien Tandel wrote:
P.S. : I would like to add binpac within this python interpreter.
But after having read the paper and thought a bit about the grammar,
I think they've used Haskell (or
Hi Steve,
I think you should have already learned it! :)
Regards,
Sebastien Tandel
On Sat, May 30, 2009 at 21:50, Stephen Fisher st...@stephen-fisher.comwrote:
On Fri, May 29, 2009 at 07:06:09PM -0300, S?bastien Tandel wrote:
These last weeks, I spent some time to integrate python into
Hi,
My apologies for not indicating what I decided to do to save you some
editing. :)
No worries, I got frustrated with the windows because of other stuff I'm
trying to do.
Regards
Anders
-Ursprungligt meddelande-
Från: wireshark-dev-boun...@wireshark.org
I just gave it a quick try on a protocol registering to udp.port.
The first problem occurred in an assert in splash_update, proposed
patch attached.
Now I get this error when opening a capture with my protocol (based on
the skeleton from the wiki page):
01:40:41 Warn Dissector bug,
I made the Lua bindings an application of the C API, not a simple
export. (e.g. proto_item and proto_tree are combined instead of dealt
individually, objects are managed in their scope so that deleted
objects are not accessed by Lua).
The reasons why I avoided just mapping the C API were many but
14 matches
Mail list logo
