Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 10328] New: SIP capture causes wireshark to crash 1.10.8

Date: Thu, 31 Jul 2014 10:58:31 +0000
Bug ID 10328
Summary SIP capture causes wireshark to crash 1.10.8
Classification Unclassified
Product Wireshark
Version 1.10.8
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 12944 [details]
SIP trace

Build Information:
Version 1.10.8 (v1.10.8-2-g52a5244 from master-1.10)

Copyright 1998-2014 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 Jun 12 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), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i5 CPU       M 560  @ 2.67GHz, with 3893MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219
--
After upgrading an older system from 1.6.6 to 1.10.8 I noticed when capturing a
SIP trace that Wireshark kept crashing. I used another system that still had
version 1.6.6 to capture and view the trace and was able to do so without a
problem. When I tried to open the attached pcap file captured from the 1.6.6
build on a Linux system with Wireshark version 1.10.8 on Windows it also crash.


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