On Sat, Jul 19, 2008 at 1:38 AM, Jaap Keuter <[EMAIL PROTECTED]> wrote:
> You can imagine that reviewing a 360kB patch takes a while. Together with
> the
> other patches in the queue, that is a lot of work we mostly do in our spare
> time.
>
Sorry, I didn't mean to rush anyone. I just wanted to
Hi,
The GTK packages have been updated please run the setup target.
Regards
Anders
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
https://wireshark.org/mailman/listinfo/wireshark-dev
Hi Steve,
That is exactly the reason we moved patch handling to bugzilla. That way
they remain stored until handled, not simply forgotten in the mail archives
of wireshark-dev.
Thanx,
Jaap
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stephen Croll
Sent: 2008-Jul-21
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/407
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Buil
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4583
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason
I'm using tcp_dissect_pdus() to dissect a TCP protocol that doesn't
include a message length field. The messages are terminated by "\r\n".
The function to return the message length is as follows:
static guint get_myproto_message_len(packet_info *pinfo, tvbuff_t *tvb,
int offset)
{
On Jul 21, 2008, at 12:51 PM, Kwan Ng [LAVA] wrote:
> I’m using tcp_dissect_pdus() to dissect a TCP protocol that doesn’t
> include a message length field. The messages are terminated by “\r
> \n”.
Then you shouldn't be using tcp_dissect_pdus(); by intent and design,
it is solely for use w
I don't have any traffic to test my dissector against, because the
components in the system that will be generating that traffic aren't
ready yet.
Until then, I've used text2pcap to construct some capture files from
scratch. There is a bit of a problem though: The -T (add TCP headers)
option resu
Hi Patrick!
Due you really need the TCP and lower layers (for example, if you make
use of the conversations API)? If not, you could simply use text2pcap
with a user DLT to test only your protocol layer:
http://wiki.wireshark.org/HowToDissectAnything (the page needs a bit
of an update to match the
