https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7318
--- Comment #22 from Guy Harris <guy@xxxxxxxxxxxx> 2012-06-14 23:18:23 PDT ---
...which is pretty much the output I'd expect in a normal case:
Got indicator 'D' from sync pipe
Adding pipe back to main loop
Removing pipe from main loop
Reading from sync pipe: fd=7
Got 0 from sync pipe, waiting for child to exit
Child process exited
NOT adding pipe back to main loop
means the capture is finishing up - a count of packet 'D'rops was sent from
dumpcap, and then dumpcap closed the pipe and exited, and Wireshark read that,
picked up the child status, and finished up.
Try checking out a fresh copy of the source from SVN and building it, and see
whether the problem still shows up. If it doesn't, I guess we close this as
fixed. If it does, try applying the patch and see what happens and what it
prints.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.