ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 51485: /trunk/ui/qt/ /trunk/ui/qt/:

From: Evan Huus <eapache@xxxxxxxxx>
Date: Thu, 22 Aug 2013 22:42:47 -0400
On Thu, Aug 22, 2013 at 10:34 PM, <gerald@xxxxxxxxxxxxx> wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=51485

User: gerald
Date: 2013/08/22 07:34 PM

Log:
 When we close a main window, delete the welcome screen, which in turn
 deletes the interface list, which in turn kills off the dumpcap process
 it may be running. This should hopefully keep us from leaving dumpcap
 processes running in the background on Windows. (Am I the only one
 running QtShark on that platform?)

You're probably the only one running it on a regular basis on any platform - I keep forgetting because my shell autocompletes ./wireshark and I hit enter before remembering to type the "-qt". You might get more takers if you made the default checkout build qt version as "wireshark", and have --enable-gtk build a "wireshark-gtk".

P.S. The valgrind step of the fuzzbot doesn't seem to be filing bugs when it errors? I don't see anything in the fuzz-test.sh script to do that, so I assume it's something you have to add on the fuzzbot side. The failure output should be exactly the same, so it's probably just a switch that needs flipping somewhere.