extcap: Fix misc memory leaks triggered by network interface changes
authorMikael Kanstrup <mikael.kanstrup@gmail.com>
Thu, 8 Sep 2016 12:26:58 +0000 (14:26 +0200)
committerPeter Wu <peter@lekensteyn.nl>
Mon, 12 Sep 2016 12:13:41 +0000 (12:13 +0000)
commitc64762d33c3a9cbc4af4040284534b440d12b210
treecd1f29e92e31ba93e19281575a1b8d4eeda7fd51
parente079862fad331cba874717ec1d0af9e35ba438b5
extcap: Fix misc memory leaks triggered by network interface changes

Valgrind reports plenty of misc memory leaks in extcap after the network
interface list has changed or is refreshed. Errors can be seen by
starting Wireshark with Valgrind's memcheck tool and bringing a network
interface up and down a few times with:

ifconfig eth0 up
ifconfig eth0 down

Change-Id: I90f53847071854b7d02facb39b7a380732de79b4
Reviewed-on: https://code.wireshark.org/review/17606
Petri-Dish: Peter Wu <peter@lekensteyn.nl>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Peter Wu <peter@lekensteyn.nl>
extcap.c
extcap.h
extcap_parser.c
extcap_spawn.c
ui/qt/extcap_options_dialog.cpp