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 looks like the seg-fault if thrown by libpcap. Has anyone else experianced the similar thing while using Wireshark 1.6.5 (im running it in Ubuntu on VirtualBox)? I got this when i start wireshark from the command line through: *./wireshark -k -i /tmp/pipe* It waits for any input from the pipe and when i did "cat capturefile.pcap > /tmp/pipe", wireshark displayed the contents partially (97 pckts out of 110) and crashed with *Segmentation fault*. On Fri, Mar 2, 2012 at 7:33 PM, vijay <vijay.prasa...@gmail.com> wrote: > Hi, > > I start wireshark from command line : "sudo ./wireshark -k -i /tmp/pipe" > > I have a capture dump in libpcap format which i wite into the pipe > (/tmp/pipe) after starting wireshark. Everytime i do this wireshark > displays the contents of the file but at the end it shows segmentation > fault. The capture file is from my previous run of wireshark saved in > libpcap format. > > Wireshark perfectly works with the same file when open though GUI. I am > using wireshark 1.6.5 on linux. Could some one pls tell me > why this behavior occurs? > > Thanks > Vijay >
___________________________________________________________________________ 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
