Bug ID |
10145
|
Summary |
Save as pcapng results in corrupt file
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.7
|
Hardware |
x86-64
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Normal
|
Priority |
Low
|
Component |
Capture file support (libwiretap)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 12781 [details]
6 packets saved as pcapng format
Build Information:
Version 1.10.7 (v1.10.7-0-g6b931a1 from master-1.10)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Apr 22 2014), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz, with 18315MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Saving a capture as type 'pcapng' results in a corrupt file that Wireshark
cannot (and/or will not) open.
Steps to reproduce:
1. Open Wireshark
2. Start capture
3. Wait for some packets
4. Stop capture
5. Save As
6. Select type pcapng
7. Save
Result:
Error dialog is shown:
The capture file appears to be damaged or corrupt.
(pcapng_read_unknown_block: total block length 0 of an unknown block type is
less than the minimum block size 12)
Expected result:
File is saved correctly and capture stays in Wireshark window.
You are receiving this mail because:
- You are watching all bug changes.