Wireshark-bugs: [Wireshark-bugs] [Bug 12787] Extcaps hang when launched from windows console
Comment # 4
on bug 12787
from Roland Knall
(In reply to Graham Bloice from comment #2)
> Regardless of the mechanism used, or issues using that mechanism, the output
> isn't as expected for a command line application on Windows.
>
> I haven't run across any other application that does this.
The question is, why does it hang. In my opinion it could be because for one of
the following reasons:
- It indeed waits for some input from a user
- It handles the closing of the pipe not properly
I am currently thinking, it is the later, as this is a mess either way. We do
not have this issue with dumpcap, as dumpcap closes the pipe, but with extcap,
this is not the case necessarily. Even if WS closes a pipe for extcap, the
utility still may wait fort the pipe to be closed, although it should have
happened already. As I have no Windows computer available most of the time,
investigation is sort of slow, as my colleague doing windows related stuff is
currently occupied. It also does not happen on every machine, only on some for
whatever reasons. I have a Win7 here where the problem occurs, and a second
Win7 (with different installed HW) where it does not.
You are receiving this mail because:
- You are watching all bug changes.
