https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2602
--- Comment #2 from Guy Harris <guy@xxxxxxxxxxxx> 2008-06-11 15:19:21 PDT ---
It's unlikely that dumpcap never captures all message traffic, if Wireshark
does capture it all, given that Wireshark has, for several releases now, used
dumpcap to do its traffic capture....
Presumably with Wireshark you started a capture and then stopped it after the
BYE message was sent, and the BYE message showed up in that capture, and with
TShark and dumpcap you started a capture and interrupted it with control-C
after the BYE message was sent, and the BYE message *didn't* show up in that
capture. If so, the capture-termination code path when dumpcap is run by
Wireshark is different from the capture-termination code path when dumpcap is
run from the command line and interrupted with control-C (and the latter is
different on Windows and UN*X), so that might be the cause of the problem.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
