Hi Joao, 2015-06-01 20:42 GMT+02:00 Joao S Veiga <jsve...@rf.com.br>: > Package: tshark > Version: 1.12.1+g01b65bf-4 > Severity: minor > > tshark consistently shows "Segmentation fault" when exiting from a capture or > capture attempt (tshark -G does not do it, but normal user without cap > permissions does it). Apart from this, it seems to work ok. > > ### exiting spontaneously: > > yankee:~# tshark -c 1 -i eth0 > Running as user "root" and group "root". This could be dangerous. > Capturing on 'eth0' > 1 0.000000 200.232.120.2 -> 216.58.222.1 TLSv1.2 211 Application Data > 1 packet captured > Segmentation fault > > ### exiting with CTRL-C: > > yankee:~# tshark -i eth0 -f 'host 200.232.120.6' > Running as user "root" and group "root". This could be dangerous. > Capturing on 'eth0' > ^C0 packets captured > Segmentation fault > > ### user without packet cap permission: > > yankee:~$ tshark -i eth0 > Capturing on 'eth0' > tshark: Couldn't run /usr/bin/dumpcap in child process: Permission denied > > 0 packets captured > Segmentation fault Please install wireshark-dbg and run "ulimit -c unlimited" before reproducing the issue. This will generate a core file which you can analyze with gdb. Please attach the stack trace to see what is crashing.
I ran a quick test on my computer and tshark ran fine. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
