Wireshark-bugs: [Wireshark-bugs] [Bug 11334] New: Clicking menu Internals->Dissector Tables cras
| Bug ID |
11334
|
| Summary |
Clicking menu Internals->Dissector Tables crashes wireshark
|
| Product |
Wireshark
|
| Version |
1.99.x (Experimental)
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
hadrielk@yahoo.com
|
Build Information:
Wireshark 1.99.8 (v1.99.8rc0-230-gb0b027d from master)
Copyright 1998-2015 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 GTK+ 3.10.8, with Cairo 1.13.1, with Pango 1.36.3, with
libpcap, with POSIX capabilities (Linux), without libnl, with libz 1.2.8, with
GLib 2.40.2, 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, with PortAudio
V19-devel (built Feb 25 2014 21:09:53), without AirPcap.
Running on Linux 3.13.0-55-generic, with locale en_US.UTF-8, 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) i7-4980HQ CPU @ 2.80GHz
Built using gcc 4.8.4.
--
Clicking Internals->Dissector Tables crashes wireshark, with the following
error:
(wireshark-gtk:22247): Gtk-CRITICAL **: gtk_tree_view_get_model: assertion
'GTK_IS_TREE_VIEW (tree_view)' failed
**
ERROR:/wireshark/ui/gtk/dissector_tables_dlg.c:154:decode_proto_add_to_list:
code should not be reached
The reason is that decode_proto_add_to_list() in dissector_tables_dlg.c
performs a switch statement for which it only handles number and string key
type for dissector tables; if the ftenum is not one of those types, it asserts.
But change 9455 (I1bca6b50), and its related changes, created a "custom"
dissector table type for custom key types - those which are not numbers or
strings but just FT_BYTES. So my assumption is that's the root cause. When I
debugged it, the assertion happened for ftenum type FT_BYTES, for table "VXI-11
Core", which is likely just the first one the function hit of this new type.
You are receiving this mail because:
- You are watching all bug changes.
