Wireshark-bugs: [Wireshark-bugs] [Bug 11122] New: "Export packet dissections > As plain text" cr
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 14 Apr 2015 22:30:36 +0000
Bug ID 11122
Summary "Export packet dissections > As plain text" crashed WireShark
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86
OS Mac OS X 10.10
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter Ralf+WireShark@Bergs.biz 

Created attachment 13561 [details]
Snoop that can be used to reproduce issue.

Build Information:
Version 1.99.6-229-g311758a (v1.99.6rc0-229-g311758a from unknown)

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.2, with libpcap, without POSIX capabilities, with
libz 1.2.3, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
without PortAudio, with AirPcap.

Running on Mac OS X 10.10.3, build 14D131 (Darwin 14.3.0), with locale C, with
libpcap version 1.5.3 - Apple version 47, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0, without AirPcap.
Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
When I open the attached snoop and try to export the packet dissection by
"Export packet dissections > As plain text" WireShark crashes reproducibly.
This doesn't happen with this snoop only, but also with others I tested. It did
NOT happen with previous builds (I'm not saying it did not happen with ANY
previous build, but it didn't happen with SEVERAL previous builds.)

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