On Mar 4, 2012, at 2:23 AM, vijay wrote: > I digged in bit further and found where the SIGSEV is signaled. Its coming > from the p_stats(). Here is what i got in gdb > > [New Thread 0xb78acb70 (LWP 3668)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb78acb70 (LWP 3668)] > 0x00f6f433 in pcap_stats () from /usr/lib/libpcap.so.0.8
Is this in Wireshark or in dumpcap? The only code I can find in the top of the 1.6 branch that calls pcap_stats() is in dumpcap. And what's the full stack trace? ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
