Bug ID |
11963
|
Summary |
HEX Value Incorrectly Saved
|
Product |
Wireshark
|
Version |
2.0.1
|
Hardware |
x86-64
|
OS |
Windows 7
|
Status |
CONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Common utilities (libwsutil)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 14200 [details]
Screen Shots
Build Information:
Wireshark 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-lice
nses/gpl-2.0.html>
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 Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows Server 2008R2 Service Pack 1, build 7601, with
locale
C, with WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), 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) Xeon(R) CPU E5-2650 v2 @ 2.60GHz (with SSE4.2), with 4095MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 31101
--
When saving the data from a followed TCP stream, all HEX values of 0x1b will be
converted to 0x2e. For example, the attached RawData.png file shows the
beginning of a print job data stream when viewed in raw format prior to saving
the data to a file. Notice that the first byte is 0x1b which is the Escape
control code. Then, look at the attached HexData.prn file which shows the
beginning of the data stream after it was saved to a file. Notice that the
first byte is now a 0x2e instead of the 0x1b as it should be.
This issue is not seen when using the previous 1.x.x versions.
You are receiving this mail because:
- You are watching all bug changes.