Wireshark-bugs: [Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after inst
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 09 Sep 2016 08:03:52 +0000

Comment # 9 on bug 12845 from 
> So, short question, if you have a hanging usbpcap and start wireshark a
> second time, can you actually capture on the shown usb devices? If so, the
> main issue is within USBPcap, although extcap should not hang.

A short answer is "yes, if I keep the zombie USBPcapCMD.exe running, start
Wireshark a second time, and start capturing on one of the USBPcapN
'interfaces', the capturing works".

The long answer is that in my case, there are three root hubs, so three
'interfaces', so the number of invocations at startup time differs.

> Could you run Wireshark through a debugger and break when it hangs, telling
> us the code-position where it is hanging? My guess would be either in
> extcap-spawn.c or in extcap.c in the code for the stderr handling.

I'm afraid the learning curve would be too lengthy as I've never done that.

Repeating the question I've asked Pascal - will it move you further if I use
the Process Monitor and tell you what the command line parameters of the zombie
instance were?

In the meantime until you answer, I'm going to install the previous USBPcap
package (...3), which requires all those reboots, and give you the feedback
whether the change from ...3 to ...5 is involved or not.

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