On Jul 10, 2015, at 10:41 AM, Hei Chan wrote:
> Thanks for your quick reply.
>
> Here is my code:
> pcap_t* m_pPcap;
> char *packet;
> struct pcap_pkthdr header;
>
> m_pPcap = pcap_open_offline(pcapFile, errbuf);
> if (pcapF
(gdb) disassemble pcap_nextDump of assembler code for function pcap_next:
0x7715a040 <+0>: sub $0x28,%rsp=> 0x7715a044 <+4>: mov
0x260(%rdi),%rdx 0x7715a04b <+11>: lea 0x18(%rsp),%rax
0x7715a050 <+16>: mov %rsi,(%rsp) 0x7715a054 <+20>:
Hi all,
I’m almost new to the network but I happened to use tcpdump for my research.
I wonder where exactly the timestamp of tcpdump comes from.
I'm working on Linux.
My best guess is that it is from net_timestamp_check() function which is
called by netif_receive_skb_internal() in net/core/dev.c
On Jul 10, 2015, at 7:53 AM, Hei Chan wrote:
> I am using libpcap 1.4.0 to read in pcap.
> And my application crashed at pcap_next() when it read the first packet from
> my pcap file:(gdb) bt#0 0x7715a044 in pcap_next () from
> /usr/lib64/libpcap.so.1
What does "disassemble pcap_next
Thanks for your quick reply.
Here is my code:pcap_t* m_pPcap;
char *packet; struct pcap_pkthdr header;
m_pPcap = pcap_open_offline(pcapFile, errbuf); if (pcapFile == NULL) {
exit(1); }
while ((packet = (char*) pcap_next(m_pPcap, &header)) != NULL) {// do my
stuffs here...}
The code above has
On Jul 10, 2015, at 7:53 AM, Hei Chan wrote:
> I am using libpcap 1.4.0 to read in pcap.
> And my application crashed at pcap_next() when it read the first packet from
> my pcap file:(gdb) bt#0 0x7715a044 in pcap_next () from
> /usr/lib64/libpcap.so.1
>
> I used wireshark to open the
Hi,
I am using libpcap 1.4.0 to read in pcap.
And my application crashed at pcap_next() when it read the first packet from my
pcap file:(gdb) bt#0 0x7715a044 in pcap_next () from
/usr/lib64/libpcap.so.1
I used wireshark to open the pcap and wireshark doesn't show any error (e.g. no
hig
[Sorry for the late response, the message was in the spam box]
On 08/06/2015 11:32, Denis Ovsienko wrote:
On Wed, 03 Jun 2015 19:12:03 +0100 Francois-Xavier Le
Bail wrote
> On 26/05/2015 15:33, Michal Sekletar wrote:
> > On 05/26/2015 11:46 AM, Francois-Xavier Le Bail wrote:
> >
The Buildbot has detected a new failure on builder tcpdump-solaris10-sparcv9
while building tcpdump.
Full details are available at:
https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-sparcv9/builds/535
Buildbot URL: https://buildfarm.opencsw.org/buildbot/
Buildslave for this Bui
The Buildbot has detected a new failure on builder tcpdump-solaris10-sparc
while building tcpdump.
Full details are available at:
https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-sparc/builds/572
Buildbot URL: https://buildfarm.opencsw.org/buildbot/
Buildslave for this Build:
>BUILD FAILED: failed shell_2
This was expected, the next commit fixed it.
--
Denis Ovsienko
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
The Buildbot has detected a new failure on builder tcpdump-solaris10-amd64
while building tcpdump.
Full details are available at:
https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-amd64/builds/533
Buildbot URL: https://buildfarm.opencsw.org/buildbot/
Buildslave for this Build:
The Buildbot has detected a new failure on builder tcpdump-solaris10-i386 while
building tcpdump.
Full details are available at:
https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-i386/builds/563
Buildbot URL: https://buildfarm.opencsw.org/buildbot/
Buildslave for this Build: un
13 matches
Mail list logo
