Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9769] New: Stack overflow after selecting data when filter is applied that has

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9769
Summary	Stack overflow after selecting data when filter is applied that has no results
Classification	Unclassified
Product	Wireshark
Version	1.10.5
Hardware	x86-64
OS	Mac OS X 10.9
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	Wireshark
Assignee	bugzilla-admin@wireshark.org
Reporter	mjbshaw@hotmail.com

Build Information:
$ wireshark --version
Object::connect: No such signal
WiresharkApplication::captureCaptureUpdateContinue(capture_options*) in
main_status_bar.cpp:170
Object::connect:  (sender name:   'wireshark')
FIX: packet list heading menu sensitivity 
wireshark 1.10.5 (SVN Rev Unknown from unknown)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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 Qt 4.8.6 with GLib 2.38.2, with libpcap, with libz
1.2.5,
without POSIX capabilities, without libnl, without SMI, with c-ares 1.10.0,
with
Lua 5.1, without Python, with GnuTLS 3.1.18, with Gcrypt 1.5.3, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Feb 15 2014 12:09:01),
with AirPcap.

Running on Mac OS X 10.9.1, build 13B42 (Darwin 13.0.0), with locale
en_US.UTF-8, with libpcap version 1.3.0 - Apple version 41, with libz 1.2.5,
GnuTLS 3.1.18, Gcrypt 1.5.3, without AirPcap.
      Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz

Built using clang 4.2.1 Compatible Apple LLVM 5.0 (clang-500.2.79).
--
I'm looking at an 802.11 capture (see attached), and when I apply a filter that
has no results:

frame contains Beacon

Then when I click the middle section of the GUI (that shows the frame
information) or the bottom section of the GUI (that shows the hex dump),
wireshark crashes. This is consistently repeatable.

I ran it in lldb, and when I did a backtrace I found there were *tons* of stack
frames, and it looks like the function proto_tree_traverse_pre_order is in some
kind of infinite recursive loop that results in a stack overflow. I have
attached the output of my lldb session.

Full steps to reproduce:

1. Start wireshark
2. Open the capture file Wireshark_802_11.pcap
3. Apply the filter "frame contains Beacon"
4. Click in the middle or bottom sections of the GUI

---

      You are receiving this mail because:

• You are watching all bug changes.