Bug 767988 - [abrt] wireshark-gnome-1.6.3-2.fc16: Process /usr/sbin/wireshark was killed by signal 11 (SIGSEGV)
Summary: [abrt] wireshark-gnome-1.6.3-2.fc16: Process /usr/sbin/wireshark was killed b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: wireshark
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Safranek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:812cb9898a2106f02eaea611d8b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-15 13:24 UTC by Andy Lindsay
Modified: 2013-02-13 15:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 15:16:40 UTC
Type: ---


Attachments (Terms of Use)
File: dso_list (10.47 KB, text/plain)
2011-12-15 13:24 UTC, Andy Lindsay
no flags Details
File: backtrace (40.25 KB, text/plain)
2011-12-15 13:24 UTC, Andy Lindsay
no flags Details
File: maps (46.03 KB, text/plain)
2011-12-15 13:24 UTC, Andy Lindsay
no flags Details

Description Andy Lindsay 2011-12-15 13:24:22 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        wireshark
crash_function: ensure_contiguous_no_exception
executable:     /usr/sbin/wireshark
kernel:         3.1.0-7.fc16.x86_64
pid:            29551
pwd:            /home/andy
reason:         Process /usr/sbin/wireshark was killed by signal 11 (SIGSEGV)
time:           Thu 15 Dec 2011 12:42:29 GMT
uid:            500
username:       andy

backtrace:      Text file, 41211 bytes
dso_list:       Text file, 10720 bytes
maps:           Text file, 47131 bytes

comment:
:I started WireShark and got the warning about not being in the WireShark group which I clicked OK because I was only going to open a previously captured file.
:
:I opened a pcap file from another server which contained a number of http requests.
:
:I used "Follow TCP conversation" to open a couple of these in separate windows.
:
:I then used Clear to remove the filter and Wireshark crashed.

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=16
:SSH_AGENT_PID=8440
:HOSTNAME=quad.ananam.com
:GPG_AGENT_INFO=/home/andy/.gnupg/S.gpg-agent:8476:1
:GLADE_PIXMAP_PATH=:
:XDG_MENU_PREFIX=xfce-
:SHELL=/bin/bash
:HISTSIZE=1000
:XDG_SESSION_COOKIE=5070883945f718cc827864474845fdbe-1322211597.116504-1336768759
:PERL5LIB=/usr/local/lib64/perl5:/usr/local/share/perl5:/usr/lib64/perl5/vendor_perl:/usr/share/perl5/vendor_perl
:QTDIR=/usr/lib64/qt-3.3
:GNOME_KEYRING_CONTROL=/tmp/keyring-yELkta
:QTINC=/usr/lib64/qt-3.3/include
:USER=andy
:GLADE_MODULE_PATH=:
:SSH_AUTH_SOCK=/tmp/ssh-nvpGruLB8422/agent.8422
:USERNAME=andy
:XDG_CONFIG_DIRS=/etc/xdg
:MAIL=/var/spool/mail/andy
:DESKTOP_SESSION=xfce
:PATH=/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/andy/bin
:PWD=/home/andy
:KDE_IS_PRELINKED=1
:LANG=en_GB.UTF-8
:GNOME_KEYRING_PID=8415
:KDEDIRS=/usr
:GDMSESSION=xfce
:SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
:HISTCONTROL=ignoredups
:SHLVL=2
:XDG_SEAT=seat0
:HOME=/home/andy
:LOGNAME=andy
:QTLIB=/usr/lib64/qt-3.3/lib
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-g9WdGfYTZ8,guid=eb77b24569ea2c4a271bb05e0000ca96
:XDG_DATA_DIRS=/usr/local/share:/usr/share
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/andy
:GLADE_CATALOG_PATH=:
:LIBGLADE_MODULE_PATH=:
:XAUTHORITY=/var/run/gdm/auth-for-andy-0OhQpz/database
:_=/usr/bin/xfce4-session
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/8487,unix/unix:/tmp/.ICE-unix/8487
:DISPLAY=:0.0

var_log_messages:
:Dec 15 12:42:28 quad kernel: [1793214.007944] wireshark[29551] general protection ip:7f4d2ffbdff2 sp:7ffff3c81b00 error:0 in libwireshark.so.1.1.0[7f4d2f039000+22b5000]
:Dec 15 12:42:30 quad abrt[29600]: Saved core dump of pid 29551 (/usr/sbin/wireshark) to /var/spool/abrt/ccpp-2011-12-15-12:42:29-29551 (105754624 bytes)

Comment 1 Andy Lindsay 2011-12-15 13:24:25 UTC
Created attachment 547236 [details]
File: dso_list

Comment 2 Andy Lindsay 2011-12-15 13:24:28 UTC
Created attachment 547237 [details]
File: backtrace

Comment 3 Andy Lindsay 2011-12-15 13:24:31 UTC
Created attachment 547238 [details]
File: maps

Comment 4 Jan Safranek 2011-12-16 08:37:33 UTC
Thanks for detailed information! Is the crash always reproducible or it happened just once? Could you please also attach the aforementioned capture file?

Comment 5 Fedora End Of Life 2013-01-16 14:21:40 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2013-02-13 15:16:45 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.