![wireshark logo](/images/wireshark-logo.png)
Wireshark mailing list archives
Re: Devices in tshark versus dumpcap
From: Gisle Vanem <gisle.vanem () gmail com>
Date: Sun, 30 Apr 2017 11:41:29 +0200
I wrote: > The is for sure a problem in how lines of text are generated in dumpcap.exe > and how tshark is interpreting them. I'm not even sure the lines have > "\r\n" terminations since from dumpcap.c: > #ifdef _WIN32 > /* set output pipe to binary mode, to avoid ugly text conversions */ > _setmode(2, O_BINARY); > > And in capchild/capture_ifinfo.c: > raw_list = g_strsplit(data, "\r\n", 0); That was the problem, Changing this into: raw_list = g_strsplit(data, "\n", 0); things work as normal! -- --gv ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Devices in tshark versus dumpcap Gisle Vanem (Apr 29)
- Re: Devices in tshark versus dumpcap Graham Bloice (Apr 29)
- Re: Devices in tshark versus dumpcap Gisle Vanem (Apr 29)
- Re: Devices in tshark versus dumpcap Graham Bloice (Apr 29)
- Re: Devices in tshark versus dumpcap Gisle Vanem (Apr 30)
- Re: Devices in tshark versus dumpcap Gisle Vanem (Apr 30)
- Re: Devices in tshark versus dumpcap Gisle Vanem (Apr 30)
- Re: Devices in tshark versus dumpcap Gisle Vanem (Apr 29)
- Re: Devices in tshark versus dumpcap Graham Bloice (Apr 29)
- <Possible follow-ups>
- Devices in tshark versus dumpcap Gisle Vanem (Apr 29)