Bug ID |
8558
|
Summary |
Incompatible fieldtypes for field with the same fieldname
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
SVN
|
Hardware |
All
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Minor
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 10537 [details]
Example Bluetooth SDP logs
Build Information:
TShark 1.9.3 (SVN Rev Unknown from unknown)
Copyright 1998-2013 Gerald Combs <[email protected]> and contributors.
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 GLib 2.32.3, with libpcap, with libz 1.2.3.4, with POSIX
capabilities (Linux), with libnl 2, with SMI 0.4.8, with c-ares 1.7.5, with Lua
5.2, without Python, with GnuTLS 2.12.14, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.
Running on Linux 3.6.9, with locale en_IE.UTF-8, with libpcap version
1.4.0-PRE-GIT_2013_03_25, with libz 1.2.3.4.
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Built using gcc 4.6.3.
--
Seems that some hf with the same fieldname
(btsdp.service_uuid in this case) may contain incompatible options
(FT_BYTES and FT_UINT16 in this case). When filtering with
"btsdp.service_uuid==5" everything is ok, but "btsdp.service_uuid==0x5" cause
the crash.
Patch: Change fieldname to avoid crash.
Maybe issue like this should be detected by tools/checkfiltername.pl or
tools/checkhf.pl (other?)
You are receiving this mail because:
- You are watching all bug changes.