Wireshark-bugs: [Wireshark-bugs] [Bug 11268] New: Crash after creating
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 11 Jun 2015 14:32:07 +0000
Bug ID 11268
Summary Crash after creating
Product Wireshark
Version 1.12.5
Hardware x86-64
OS Fedora
Status UNCONFIRMED
Severity Critical
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter victor.engmark@gmail.com 

Build Information:
$ wireshark -v
wireshark 1.12.5 (Git Rev Unknown from unknown)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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.27, with Cairo 1.14.2, with Pango 1.36.8, with
GLib 2.42.2, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
without libnl, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without
Python,
with GnuTLS 3.3.14, with Gcrypt 1.6.3, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Aug 18 2014 05:50:44), with AirPcap.

Running on Linux 4.0.4-202.fc21.x86_64, with locale en_GB.utf8, with libpcap
version 1.7.2, with libz 1.2.8, GnuTLS 3.3.15, Gcrypt 1.6.3, without AirPcap.
      Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz

Built using gcc 4.9.2 20150212 (Red Hat 4.9.2-6).

--
To reproduce:

1. Start Wireshark
2. Press Ctrl-Shift-p
3. Go to Protocols -> SSH
4. Press the "Edit..." button next to "RSA keys list"
5. Press New
6. Fill in IP address "198.252.206.16", port "443", protocol "http"
7. Press OK
8. Press OK

At this point Wireshark crashed with the following message:

$ wireshark
(wireshark:25091): GLib-ERROR **: gmem.c:103: failed to allocate
9223372036854775807 bytes
Trace/breakpoint trap (core dumped)

Some differences from bug 11031:

- 100% reproducible across three tries.
- Subsequent runs *always* crash with the same message.
- This crash happens even if there is no running or open trace.

After `rm ~/.wireshark/ssl_keys` Wireshark starts again.

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