Argh, nevermind. I think the corrupted packet caused my application to have some invalid read/write, corrupting something pcap_next() is going to use and so I thought it crashed inside pcap_next().
Sorry for the false alarm. On Thursday, October 23, 2014 2:14 AM, Guy Harris <g...@alum.mit.edu> wrote: On Oct 18, 2014, at 4:12 AM, Hei Chan <structurech...@yahoo.com> wrote: > Hi, > The first 3 packets are corrupted according to wireshark. What is the exact message Wireshark reports? Can you send us the pcap file or make it available for downloading? > As soon as I read the first packet with pcap_next(), my application gets a > coredump. Is it crashing in pcap_next(), or is it crashing in your application's code? Could we see your application's code? If it's crashing in pcap_next(), what is the stack trace from the crash? _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
