Re: [Wireshark-commits] rev 37846: /trunk/ /trunk/: dumpcap.c
On Jul 1, 2011, at 8:41 PM, Guy Harris wrote:
> On Jun 30, 2011, at 1:18 PM, gerald@... wrote:
>> User: gerald
>> Date: 2011/06/30 01:18 PM
>> Log the success or failure of pcap_open/pcap_create/pcap_open_live.
> So, err, umm, is WinPcap's pcap_open_live() - well, you probably have a recent version of WinPcap, so it
might be pcap_activate() inside pcap_open_live() - hanging, crashing, or *what* when you hand it "-" as
an argument? It *should* just quickly fail, so that dumpcap can fall back on "I guess that's a pipe".
Actually I guess that WinPcap's pcap_open_live() somehow calls exit(127)... Not
that I expect WinPcap to call exit() at all, I have no clue why this behavior
now shows up and not earlier... All parameters provided to the pcap_open_live()
call make sense (to me)...
> Sent via: Wireshark-dev mailing list <wireshark-dev@...>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
Sent via: Wireshark-dev mailing list <wireshark-dev@...>