Johan Mazel a écrit :
The size of pcap_payload is always -1. This means that we can never access to
the data inside the packet.
Actually, pcap_payload embeds a pointer outside the ML heap (ML block
with unaligned_tag). I guess it is the libpcap receive buffer. As such,
it is not marshallable
Hi
2010/1/8 Stéphane Glondu st...@glondu.net
Johan Mazel a écrit :
The size of pcap_payload is always -1. This means that we can never
access to the data inside the packet.
Actually, pcap_payload embeds a pointer outside the ML heap (ML block
with unaligned_tag). I guess it is the libpcap
Johan Mazel wrote:
I think that the original code, the one that have been used to build the
debian
package, is the one from this this website:
http://www.drugphish.ch/~jonny/mlpcap.html
http://www.drugphish.ch/%7Ejonny/mlpcap.html. I figured it because the file
mlpcap_0.9.orig.tar.gz
Hi
I just tried to install manually libmlpcap-ocaml-dev.
And, the behavior is the same, I still have the -1 as size for pcap_payload.
So, I understand, this is not a bug.
What is the procedure, to set this bug report as solved or non-relevant ?
Thanks for your time.
Regards
Johan Mazel
Package:libmlpcap-ocaml-dev
Version 0.9-13
I'm trying to read a trace obtained through wireshark.
I use pcap_loop to launch a callback function.
The call function is supposed to look like something similar to this:
let callback_process _ pkt_hdr pcap_payload =
The type of pkt_hdr is
5 matches
Mail list logo
