Wireshark-bugs: [Wireshark-bugs] [Bug 5871] System lockup when a packet is viewed
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5871
--- Comment #1 from Steve <temp636@xxxxxxxxxxxx> 2011-04-29 00:21:53 PDT ---
Additional comment from Steve (temp636@xxxxxxxxxxxx)...
I forgot to include the Wireshark "about" info. My laptop (Compaq Presario
CQ56) which is running Wireshark is offline now. But I can still copy what I
see on the Wireshark About screen and transcribe it.
Compiled (64-bit) with GTK+ 2.16.6 with Glib 2.22.4 with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3, with
Gcrypt 1.4.6, without Keberos, with GeoIP, with PortAudio V19-devel (built Apr
15,2011), with AirPcap.
Running on 64-bit Windows 7, build 7600, with WinPcap version 4.12 (packet.dll
version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 21022
Hope this helps...
Steve.
Feel free to email me at temp636@xxxxxxxxxxxx if you think I may help any more
in resolving this. I am still able to repeatedly hang up my machine on the
packet file I captured. When I viewed packet 13, then viewed packet 12, it
will hang and force me to exit Wireshark while Windows gives me hang-up report
which I had cut and pasted to my initial entry.
If I am being too verbose with this, let me know. I don't wanna be a pain in
the arse, but being a former repairman, I will do my darndest to do what I
wanted my clients to do - that is show me exactly what they did to make it
misbehave.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
