Wireshark-bugs: [Wireshark-bugs] [Bug 12103] New: dll dissector plugin makes Wireshark crash dur

Date: Tue, 09 Feb 2016 18:36:47 +0000
Bug ID 12103
Summary dll dissector plugin makes Wireshark crash during startup
Product Wireshark
Version 2.0.1
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Critical
Priority Low
Component Qt UI
Assignee [email protected]
Reporter [email protected]

Created attachment 14313 [details]
dll file to add to plugins directory

Build Information:
Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)

Copyright 1998-2015 Gerald Combs <[email protected]> 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 (32-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.38.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
       Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (with SSE4.2), with 8098MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 31101

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Hello,
I am working with Bluetooth sniffer from Nordic semiconductor.
https://www.nordicsemi.com/eng/Products/Bluetooth-Smart-Bluetooth-low-energy/nRF-Sniffer
The tool adds the attached dll to \plugins\2.0.1\ folder and wireshark is not
able to startup anymore (crash at mid-startup). Once the dll file deleted, all
works fine again.

Note that the sniffer is working well with version 2.0.0 and 1.12.9. This makes
me think that the bug comes from wireshark.


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