Your message dated Sat, 21 Nov 2015 23:20:20 +0100
with message-id <[email protected]>
and subject line Re: Bug#787447: tshark shows 'Segmentation fault' on exit
has caused the Debian Bug report #787447,
regarding tshark shows 'Segmentation fault' on exit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
787447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787447
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
### tcpdump does not segfault:
yankee:~# tcpdump -c 1 -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:40:40.516859 IP tlp-us-mid.apache.org.http > yankee.rf.com.br.60602: Flags
[P.], seq 937874142:937875590, ack 2881740789, win 235, options [nop,nop,TS val
375110833 ecr 671335743], length 1448
1 packet captured
243 packets received by filter
0 packets dropped by kernel
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages tshark depends on:
ii libc6 2.19-18
ii libglib2.0-0 2.42.1-1
ii libpcap0.8 1.6.2-2
ii libwireshark5 1.12.1+g01b65bf-4
ii libwiretap4 1.12.1+g01b65bf-4
ii libwsutil4 1.12.1+g01b65bf-4
ii wireshark-common 1.12.1+g01b65bf-4
ii zlib1g 1:1.2.8.dfsg-2+b1
tshark recommends no packages.
tshark suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 2.0.0~rc2+g74e5b56-1
On Thu, 4 Jun 2015 23:19:02 +0200 =?UTF-8?B?QsOhbGludCBSw6ljemV5?=
<[email protected]> wrote:
...
> 2015-06-02 13:54 GMT+02:00 Joao S Veiga <[email protected]>:
...
> > Please let me know if you need any more information or tests.
> Thank you, this seems to be enough to fix the issue.
And the fix finally reached Debian, too. :-)
Cheers,
Balint
--- End Message ---
