https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845
David W Walters <walte...@comcast.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |INCOMPLETE
--- Comment #42 from David W Walters <walte...@comcast.net> ---
(In reply to Roland Knall from comment #41)
> (In reply to David W Walters from comment #34)
> > Not able to build a development version to try at this time. Downloading
> > all the tools needed, but it will take a while to get set up. Is there a
> > patch version available that I can test??
>
> As it is merged now, you can download the latest daily-build from
> https://www.wireshark.org/download/automated/win64/ and try it out. I would
> take the latest 2.5.0, which will become 2.6 at some point. 2.4 you could
> try as well. Let us know, if it really fixed it for you.
I tried the latest build, and it still locks up. I have done further
investigation, and it appears like there is a buffer limit of 4K on stdio.
This article states that fact:
https://stackoverflow.com/questions/2066242/is-there-a-buffer-size-attached-to-stdout.
I have also re-built USBPcapCMD to limit its output to less than 4096 char,
and now Wireshark does not lock up any more, although there appears to be some
other issues that result in a "Selected capture options result in empty
capture." message from USBPcapCMD. I will investigate further.
I do not have any recommendation as to how to fix this buffer size limitation
issue as yet.
Feel free to contact me to discuss.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
