Wireshark-bugs: [Wireshark-bugs] [Bug 11442] New: GVCP bit-fields not updated
Date: Thu, 13 Aug 2015 11:36:41 +0000
Bug ID 11442
Summary GVCP bit-fields not updated
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Minor
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter nine-wireshark.org@wirdorange.org

Created attachment 13796 [details]
Screenshot

Build Information:
Version 1.99.8 (v1.99.8-0-ga0c561a from master)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/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.1, with WinPcap (unknown), 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, without PortAudio,
with AirPcap.

Running on 64-bit Windows 7 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) Core(TM) i7-4790 CPU @ 3.60GHz (with SSE4.2), with 16318MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 31101
--
When writing to special GVCP registers, e.g. SCPS0, the bit-fields are not
parsed correctly. 

Please find an example below and as an attached screenshot. The original
register-value is 0xC0000200, but is displayed as 0x00000200.


Example:

Bootstrap Register: [SCPS0 (Stream Channel #0 Packet Size)] (0x00000d04)
    0... .... .... .... .... .... .... .... = Fire Test Packet: False
    .0.. .... .... .... .... .... .... .... = Do Not Fragment: False
    ..0. .... .... .... .... .... .... .... = Pixel Endianness: False
    .... .... .... .... 0000 0010 0000 0000 = Packet Size: 512


You are receiving this mail because:
  • You are watching all bug changes.