Wireshark-bugs: [Wireshark-bugs] [Bug 12386] New: Wireshark crash cleaning up subnet entries aft

Date: Thu, 28 Apr 2016 03:25:01 +0000
Bug ID 12386
Summary Wireshark crash cleaning up subnet entries after preference change
Product Wireshark
Version Git
Hardware All
OS All
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Build Information:
git
--
Using the HTTP capture from 10335 I'm getting crashes every time I change the
preference "allow subdissectors to reassemble TCP streams" or whatever.

Backtrace is:

gdb) bt
#0  0x00007ffff4ef36ce in wmem_block_free (allocator=0x12e0d60,
block=0x2df03f0) at ../../../epan/wmem/wmem_allocator_block.c:745
#1  0x00007ffff4ef36ce in wmem_block_free (chunk=0x2df0400,
allocator=0x12e0d60) at ../../../epan/wmem/wmem_allocator_block.c:822
#2  0x00007ffff4ef36ce in wmem_block_free (private_data=0x12e0d60,
ptr=0x2df0410) at ../../../epan/wmem/wmem_allocator_block.c:913
#3  0x00007ffff4380617 in cleanup_subnet_entry (entry=0x2e002e0) at
../../epan/addr_resolv.c:2357
#4  0x00007ffff4380617 in cleanup_subnet_entry (entry=0x2e2fae0) at
../../epan/addr_resolv.c:2357
#5  0x00007ffff4380617 in cleanup_subnet_entry (entry=0x2e7af00) at
../../epan/addr_resolv.c:2357
#6  0x00007ffff4380617 in cleanup_subnet_entry (entry=0x1f059d0) at
../../epan/addr_resolv.c:2357
#7  0x00007ffff438274f in host_name_lookup_cleanup () at
../../epan/addr_resolv.c:2738
#8  0x00007ffff439c38b in cleanup_dissection () at ../../epan/packet.c:317
#9  0x00007ffff439284e in epan_free (session=0x2cf9540) at
../../epan/epan.c:233
#10 0x000000000045641a in rescan_packets (cf=0xc3a060 <cfile>,
action="" "Reprocessing",
action_item=action_item@entry=0x76e5fb "all packets",
redissect=redissect@entry=1)
    at ../file.c:1623
#11 0x0000000000456838 in cf_redissect_packets (cf=<optimized out>) at
../file.c:1490
#12 0x000000000049caf9 in MainWindow::redissectPackets() (this=0xdfcb10) at
../../../ui/qt/main_window_slots.cpp:1323
#13 0x00000000005b1eef in MainWindow::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0xdfcb10, _c=<optimized out>,
_id=<optimized out>, _a=0x4036670) at main_window.moc.cpp:1421
#14 0x00007ffff0af9161 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#15 0x00007ffff1ad316b in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#16 0x00007ffff1be944b in QMainWindow::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#17 0x00007ffff1a9041c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#18 0x00007ffff1a958e6 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#19 0x00007ffff0ac973b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#20 0x00007ffff0acbb36 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#21 0x00007ffff0b1faa3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#22 0x00007ffff247be3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#23 0x00007ffff247c1d0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#24 0x00007ffff247c27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#25 0x00007ffff0b1feaf in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib64/libQt5Core.so.5
#26 0x00007ffff0ac6eca in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib64/libQt5Core.so.5
#27 0x00007ffff0acefac in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#28 0x0000000000447a66 in main(int, char**) (argc=0, argv=<optimized out>) at
../wireshark-qt.cpp:1415


I do have a ~/.wireshark/subnets file which contains:

10.1.1.0/24             SiteA
10.1.2.0/24             SiteB1
10.1.3.0/24             SiteC
10.2.0.0/16             SiteD
10.3.0.0/20             SiteB2
10.3.16.0/20            SiteF
10.3.32.0/20            SiteG
10.3.64.0/20            SiteF2
10.3.128.0/20           SiteH

(Presumably left over from some other test.)  Removing that file makes the
crash go away.


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