https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Michael Mann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Pascal Quantin changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #35 from Gerrit Code Review ---
Change 32870 merged by Anders Broman:
wsutil: Read stderr and stdout data asynchronously
https://code.wireshark.org/review/32870
--
You are receiving this mail because:
You are watching all bu
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #34 from Gerrit Code Review ---
Change 32870 had a related patch set uploaded by Pascal Quantin:
wsutil: Read stderr and stdout data asynchronously
https://code.wireshark.org/review/32870
--
You are receiving this mail becau
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #33 from Gerrit Code Review ---
Change 32773 merged by Anders Broman:
wsutil: Read stderr and stdout data asynchronously
https://code.wireshark.org/review/32773
--
You are receiving this mail because:
You are watching all bu
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #32 from Gerrit Code Review ---
Change 32773 had a related patch set uploaded by Tomasz Moń:
wsutil: Read stderr and stdout data asynchronously
https://code.wireshark.org/review/32773
--
You are receiving this mail because:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #31 from vgold ---
Addition: the value you mentioned has been changed in the test version from 100
ms to 1 ms.
--
You are receiving this mail because:
You are watching all bug changes._
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #30 from vgold ---
(In reply to Tomasz Mon from comment #29)
> In wsutil/ws_pipe.c there is the code:
> /* Keep peeking at pipes every 100 ms. */
> dw = WaitForSingleObject(processInfo.hProcess, 10)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #29 from Tomasz Mon ---
@vgold Are you able to compile Wireshark yourself? If yes, could you please try
reducing the timeout interval to WaitForSingleObject() in wsutil/ws_pipe.c
In wsutil/ws_pipe.c there is the code:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #28 from Tomasz Mon ---
I have just released USBPcap 1.3.0.0 which might improve the situation a bit.
If you observe the hang with USBPcap 1.3.0.0, please email me the memory dump
of USBPcapCMD for analysis.
--
You are receiv
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
vg...@mail.ru changed:
What|Removed |Added
CC||vg...@mail.ru
--- Comment #27 from
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #26 from Tomasz Mon ---
@walitab Could you please reproduce the issue, wait some time and then create
memory dump of USBPcapCMD process (it is one of the options after right
clicking on process in Task Manager) and email it to
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
walitab changed:
What|Removed |Added
CC||ranuber...@gmx.net
--- Comment #25 from
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #24 from Gerrit Code Review ---
Change 29167 merged by Roland Knall:
Do not pass pipe handle to WaitForMultipleObjects
https://code.wireshark.org/review/29167
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #23 from Gerrit Code Review ---
Change 29167 had a related patch set uploaded by Roland Knall:
Do not pass pipe handle to WaitForMultipleObjects
https://code.wireshark.org/review/29167
--
You are receiving this mail because:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #22 from Gerrit Code Review ---
Change 29163 merged by Roland Knall:
Do not pass pipe handle to WaitForMultipleObjects
https://code.wireshark.org/review/29163
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #21 from Gerrit Code Review ---
Change 29161 merged by Roland Knall:
Fix extcap initialization deadlock
https://code.wireshark.org/review/29161
--
You are receiving this mail because:
You are watching all bug changes.___
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #20 from Gerrit Code Review ---
Change 29163 had a related patch set uploaded by Tomasz Moń:
Do not pass pipe handle to WaitForMultipleObjects
https://code.wireshark.org/review/29163
--
You are receiving this mail because:
Y
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #19 from Gerrit Code Review ---
Change 29161 had a related patch set uploaded by Roland Knall:
Fix extcap initialization deadlock
https://code.wireshark.org/review/29161
--
You are receiving this mail because:
You are watchi
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #18 from Gerrit Code Review ---
Change 29159 merged by Roland Knall:
Fix extcap initialization deadlock
https://code.wireshark.org/review/29159
--
You are receiving this mail because:
You are watching all bug changes.___
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #17 from Gerrit Code Review ---
Change 29159 had a related patch set uploaded by Tomasz Moń:
Fix extcap initialization deadlock
https://code.wireshark.org/review/29159
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #16 from Tomasz Mon ---
After checking the ws_pipe_spawn_sync() the explaination seems plausible. The
way it works on Windows is:
1. Create stdout and stderr pipes
2. Execute extcap redirecting the stdout and stderr to created
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #15 from Tomasz Mon ---
The dump file that I have received so far indicates that USBPcapCMD is stuck at
printf("value {arg=%d}{value=%d_%d}{display=%s}{enabled=false}", ...)
This seems very strange to me. Does Wireshark wait f
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Tomasz Mon changed:
What|Removed |Added
CC||deso...@gmail.com
--- Comment #14 fr
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #13 from Gerrit Code Review ---
Change 29154 had a related patch set uploaded by Pascal Quantin:
Windows: upgrade USBPcap to 1.2.0.4
https://code.wireshark.org/review/29154
--
You are receiving this mail because:
You are wat
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #12 from Pascal Quantin ---
USBPcap 1.2.0.4 is now out. I will add it soon to the installer.
In the meantime you can install it manually, and then copy USBPcapCMD from
USBPcap installation folder in C:\Program Files\Wireshark\e
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #11 from Pascal Quantin ---
USBPcap is not installed by default, and has a warning in Wireshark installer
page. So it should not get installed by clicking on the options without reading
them. Moreovers like only a few people a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #10 from Dylan ---
Pascal: If that bug on the github page is what is causing this Wireshark bug,
could you add some extra warning/error to the updated Wireshark installer like
"You must uninstall USBPcap versions < 1.2.0.4" ?
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Pascal Quantin changed:
What|Removed |Added
CC||pascal.quan...@gmail.com
--- Com
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Dylan changed:
What|Removed |Added
Ever confirmed|0 |1
Priority|Low
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Jeremy Elliott changed:
What|Removed |Added
CC||jeremy3elliott...@gmail.com
---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Dylan changed:
What|Removed |Added
CC||daul...@gmail.com
--- Comment #6 from Dyl
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
daniel.ke...@gmail.com changed:
What|Removed |Added
CC||daniel.ke...@gmail.com
--
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Dan Lukes changed:
What|Removed |Added
OS|Windows 10 |Windows
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
Michael Lococo changed:
What|Removed |Added
CC||michael_loc...@hotmail.com
--- C
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #2 from white...@hotmail.com ---
when i looked at the properties of the USBCap, the double slashes seemed to me
an oddity. i admit ignorance here, so if it's nothing, then okay. but stood
out to me as odd.
also, this UI for s
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
--- Comment #1 from white...@hotmail.com ---
Created attachment 16310
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16310&action=edit
Wireshark-USBCap in ProcExp64
--
You are receiving this mail because:
You are watching all
37 matches
Mail list logo
