https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15205
--- Comment #9 from Stig Bjørlykke <s...@bjorlykke.org> ---
(In reply to Guy Harris from comment #8)
> Then you'd better make sure the stderr pipe is closed after the message is
> written, otherwise the behavior of ws_read_string_from_pipe() will be
> unpredictable.
The stderr pipe is created by g_spawn_async_with_pipes() and must be closed by
the caller, which is the Wireshark extcap handling code. Therefore we can't
ensure this pipe is closed after the message is written.
Remember that the extcap utility may be written by a user, and we should not
loop infinite even if the extcap utility misbehaves.
--
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
