https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15205
Stig Bjørlykke <s...@bjorlykke.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #12 from Stig Bjørlykke <s...@bjorlykke.org> ---
(In reply to Guy Harris from comment #11)
> So how do you know when you have the entire message string? Do you just
> hope that a single read from the pipe will deliver the entire message?
I did not design or refactor this code, I just want to avoid the infinite loop
reading stderr from the extcap utility. We are about to close the extcap
utility using g_spawn_close_pid() so I suppose we just read whatever is in the
pipe before closing. This is a better feedback to the user than presenting
nothing.
--
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
