[Moving thread to wireshark-dev from wireshark-core, following Joerg's action]
I have just committed the make target dumpabi for dumping ABI
description using ABI compliance checker [1].
Now everything is there to start versioning with as little effort as possible.
Cheers,
Balint
[1]
Hi Joerg,
On 05/31/2011 12:02 AM, Joerg Mayer wrote:
[Moved this to wireshark-dev as it still does not belong onto
wireshark-core]
On Mon, May 30, 2011 at 04:18:31PM +0200, Balint Reczey wrote:
I still don't know how it works when we don't install header files,
network except have copy of
On Wed, May 18, 2011 at 02:17:33PM -0400, Ed Beroset wrote:
Speaking of more limited platforms, I wonder about about a way of
reducing both startup time and memory usage by having the dissectors
dynamically loaded (as with the current plug-in mechanism) rather than
statically linked. The
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark 1.2.
Full details are available at:
http://buildbot.wireshark.org/trunk-1.2/builders/Windows-XP-x86/builds/9
Buildbot URL: http://buildbot.wireshark.org/trunk-1.2/
Buildslave for this Build: windows-xp-x86
Build Reason:
On Tue, May 31, 2011 at 11:54:16AM -0600, Stephen Fisher wrote:
On Wed, May 18, 2011 at 02:17:33PM -0400, Ed Beroset wrote:
Speaking of more limited platforms, I wonder about about a way of
reducing both startup time and memory usage by having the dissectors
dynamically loaded (as with
On Mon, May 23, 2011 at 02:41:57PM -0400, Brian Oleksa wrote:
If I have a field that I am trying to dissect that has a max field
size of 8192 bits.
What data structure should I put this into..??
Perhaps FT_BYTES, FT_UINT_BYTES .
It depends what the information is and what you
Jakub Zawadzki skrev 2011-05-31 20:54:
On Tue, May 31, 2011 at 11:54:16AM -0600, Stephen Fisher wrote:
On Wed, May 18, 2011 at 02:17:33PM -0400, Ed Beroset wrote:
Speaking of more limited platforms, I wonder about about a way of
reducing both startup time and memory usage by having the
On Tue, May 31, 2011 at 09:49:32PM +0200, Anders Broman wrote:
Should we first formulate what the goal [...]
Of course for me primary goal is faster compiling of wireshark ;-)
(it's real pain when I change single .h file and I must wait
to recompile libdissectors :-)
But I think for others
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm proud to announce the release of Wireshark 1.2.17.
What is Wireshark?
Wireshark is the world's most popular network protocol analyzer.
It is used for troubleshooting, analysis, development, and
education.
What's New
Bug Fixes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm proud to announce the release of Wireshark 1.4.7.
What is Wireshark?
Wireshark is the world's most popular network protocol analyzer.
It is used for troubleshooting, analysis, development and
education.
What's New
Bug Fixes
The
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/1452
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: ubuntu-10.04-x64
Build
On Mar 24, 2011, at 12:01 AM, Roland Knall wrote:
Hello
The dissectory has now been fuzz-tested as well, with nearly 250 MB
worth of various capture files. It passed.
The updated version of the patch is online.
It's checked in.
Unfortunately, the openSAFETY dissector, which is a
Hello
On Wed, Jun 1, 2011 at 5:27 AM, Guy Harris g...@alum.mit.edu wrote:
However, if this is the cause of
http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/1452/steps/fuzz-menagerie/logs/stdio
then that raises the question why isn't the SERCOS III plugin being
13 matches
Mail list logo
