Wireshark-bugs: [Wireshark-bugs] [Bug 10290] New: GTK Capture Dialog crashes with DLT 147
Date: Fri, 18 Jul 2014 07:51:36 +0000
Bug ID 10290
Summary GTK Capture Dialog crashes with DLT 147
Classification Unclassified
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86
OS Ubuntu
Status UNCONFIRMED
Severity Normal
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter rknall@gmail.com

Build Information:
TShark (Wireshark) 1.99.0 (v1.99.0-rc1-919-ga4cd488 from unknown)

Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), without libnl,
with libz 1.2.8, with GLib 2.40.0, with SMI 0.4.8, with c-ares 1.10.0, with Lua
5.2, with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP.

Running on Linux 3.13.0-24-generic, with locale en, with libpcap version 1.5.3,
with libz 1.2.8, with GnuTLS 2.12.23, with Gcrypt 1.5.3.
Intel(R) Core(TM)2 Quad CPU    Q8400  @ 2.66GHz

Built using gcc 4.8.2.

--
Alexis La Goutte pointed out to me, that when using extcap, the "Capture
Dialog" crashes after selecting a Capture Filter, with BPF compiling enabled.
It does not crash on me on OSX, where BPF compiling is not enabled.

It seems, that pcap_parse crashes in libpcap 0.8 (Ubuntu 14.04 stock install),
if DLT is 147. DLT 1 works fine. I have tested this with the extcap extension,
although I assume, this has nothing to do with extcap in particular. 

If the extcap plug-in tells ws, that it's DLT is 147 WS crashes upon selection
of an interface. If the extcap plug-in sends no DLT or DLT 1(EN10MB) WS does
not crash, and the BPF compilation works as it should.

I have filed a bug with pcap
(https://github.com/the-tcpdump-group/libpcap/issues/368), but I am not sure if
it is a bug in pcap, or in the UI, as maybe the UI should prevent calling
pcap_parse if the DLT is not valid or user-defined. The best way to test this
is with extcap (I4f1239b2f1ebd8b2969f73af137915f5be1ce50f)


You are receiving this mail because:
  • You are watching all bug changes.