ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 9106] New: Wireshark crashes when using "Export Specified

Date: Thu, 05 Sep 2013 15:43:26 +0000
Bug ID 9106
Summary Wireshark crashes when using "Export Specified Packets" > "Displayed"
Classification Unclassified
Product Wireshark
Version 1.11.x (Experimental)
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Wireshark
Assignee [email protected]
Reporter [email protected]

Build Information:
$ wireshark -v
wireshark 1.11.0-SVN-51784 (SVN Rev 51784 from /trunk)

Copyright 1998-2013 Gerald Combs <[email protected]> and contributors.
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 GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Sep  5 2013), 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), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz, with 5937MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219
--
Wireshark version 1.11.0-SVN-XXXXX has been crashing every time I try to save a
subset of packets with File -> Export Specified Packets -> Packet Range ->
Displayed.  This happens with every capture file I try it with, so I'm hoping
that it's easy to reproduce, but I'm happy to provide any logs that are
necessary to help out with this if you can tell me where to find crash logs,
etc.


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