| Bug ID |
10348
|
| Summary |
Different dissection results for same file
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.99.x (Experimental)
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 12961 [details]
Sample capture file showing the described behaviour
Build Information:
Version 1.99.0 (v1.99.0-rc1-1180-gf080b43 from unknown)
Copyright 1998-2014 Gerald Combs <[email protected]> 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 (32-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
WinPcap (4_1_3), with libz 1.2.5, with GLib 2.38.0, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, with GnuTLS 3.1.22, with Gcrypt 1.6.0, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Aug 5 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), with GnuTLS 3.1.22, with Gcrypt 1.6.0, without AirPcap.
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz (with SSE4.2), with 8132MB of
physical memory.
Built using Microsoft Visual C++ 9.0 build 21022
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Steps to reproduce:
- Start Wireshark
- Open attached capture file
--> Frame No. 11 shows correctly as WriteResponse
- Close capture file (don't close Wireshark)
- Open attached capture file again
--> Frame No. 11 shows as (Message fragment 54) without being disassembled
When opening the capture file for the second time, the dissector seems to be in
a different state than on the first time, as the WriteResponse is not displayed
correctly.
You are receiving this mail because:
- You are watching all bug changes.