Comment # 8
on bug 13175
from Pavel Sindelka
(In reply to Pascal Quantin from comment #7)
> You were using Wireshark 2.2.2 x64, right?
As I'm not the one who has open the ticket, here is my quote from About
Wireshark:
Version 2.2.2 (v2.2.2-0-g775fb08)
Compiled (64-bit) with Qt 5.6.1, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 10, build 14393, with locale Czech_Czech
Republic.1250, with WinPcap version 4.1.3 (packet.dll version 0.08), based on
libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with
Gcrypt
1.6.2, without AirPcap.
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (with SSE4.2), with 8141MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
> So out_fd is equal to 0x3BA70000 (which is not a negative number)
> and in_file_count is equal to 2...
I'm not sure whether you expect any reaction to this?
You are receiving this mail because:
- You are watching all bug changes.