What    |Removed                     |Added
         Resolution|FIXED                       |---
             Status|RESOLVED                    |INCOMPLETE

--- Comment #7 from ---
I've just tried the latest build (Wireshark-win64-2.3.0-3223-gb0c48f3, more
information below).

The error message in the packet list has disappeared. It looks like a normal
ATT Packet now.

But Wireshark still crashes when I try to select one of the packets (either by
mouse click or by selecting it with the arrow keys on the keyboard).

The Windows error Report looks like this (roughly translated from German):

Problem signature:
  Problem event name:   BEX64
  Application name:     Wireshark.exe
  Application version:
  Application time stamp:       58f83312
  Error module name:    libwireshark.dll
  Error module version:
  Error module time stamp:      58f83108
  Exception Offset:     0000000000e6d88c
  Exception Code:       c0000409
  Exception Data:       0000000000000000
  OS Version:   6.1.7601.
  Locale-ID:    1031
  Additional Information 1:     aba7
  Additional Information 2:     aba7b85adbcf9f8f5a12c97cebf3ea2d
  Additional Information 3:     a68d
  Additional Information 4:     a68d3c9d249ca78566e9c65259ba8a80

Version 2.3.0-3223-gb0c48f3 (v2.3.0rc0-3223-gb0c48f3)

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.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0,
with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap,
SBC, with SpanDSP.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with        Intel(R)
Core(TM) i5-2410M CPU @ 2.30GHz (with SSE4.2), with 8086 MB of physical memory,
with locale German_Germany.1252, with WinPcap version 4.1.3 (packet.dll version, based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.4.11, with Gcrypt 1.7.6, without AirPcap.

Built using Microsoft Visual C++ 12.0 build 40629

You are receiving this mail because:
You are watching all bug changes.
Sent via:    Wireshark-bugs mailing list <>

Reply via email to