Bug 884882

Summary: [abrt] wireshark-1.6.11-1.fc17: vasprintf: Process /usr/sbin/dumpcap was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Mads Kiilerich <mads>
Component: wiresharkAssignee: Peter Hatina <phatina>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: huzaifas, jsafrane, mads, mapcode.mind, phatina, rvokal, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e00738f3ef64d771a33d97d28ee06971943fbd51
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 08:32:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data none

Description Mads Kiilerich 2012-12-06 22:23:12 UTC 
Version-Release number of selected component:
wireshark-1.6.11-1.fc17

Additional info:
backtrace_rating: 4
cmdline:        /sbin/dumpcap -i eth0 -Z none -B 1 -f 'port 1935'
crash_function: vasprintf
executable:     /usr/sbin/dumpcap
kernel:         3.6.6-1.fc17.i686.PAE
remote_result:  NOTFOUND
uid:            0
var_log_messages: Nov 25 20:26:15 D610 abrt[1408]: Saved core dump of pid 1361 (/usr/sbin/dumpcap) to /var/spool/abrt/ccpp-2012-11-25-20:26:15-1361 (495616 bytes)

Truncated backtrace:
Thread no. 1 (5 frames)
 #19 vasprintf at /usr/include/bits/stdio2.h:199
 #20 g_vasprintf at gprintf.c:314
 #21 g_strdup_vprintf at gstrfuncs.c:509
 #24 report_packet_drops at dumpcap.c:4136
 #25 capture_loop_start at dumpcap.c:3193
Comment 1 Mads Kiilerich 2012-12-06 22:23:17 UTC 
Created attachment 659072 [details]
File: backtrace
Comment 2 Mads Kiilerich 2012-12-06 22:23:19 UTC 
Created attachment 659073 [details]
File: cgroup
Comment 3 Mads Kiilerich 2012-12-06 22:23:21 UTC 
Created attachment 659074 [details]
File: core_backtrace
Comment 4 Mads Kiilerich 2012-12-06 22:23:23 UTC 
Created attachment 659075 [details]
File: dso_list
Comment 5 Mads Kiilerich 2012-12-06 22:23:25 UTC 
Created attachment 659076 [details]
File: environ
Comment 6 Mads Kiilerich 2012-12-06 22:23:28 UTC 
Created attachment 659077 [details]
File: limits
Comment 7 Mads Kiilerich 2012-12-06 22:23:30 UTC 
Created attachment 659078 [details]
File: maps
Comment 8 Mads Kiilerich 2012-12-06 22:23:31 UTC 
Created attachment 659079 [details]
File: open_fds
Comment 9 Mads Kiilerich 2012-12-06 22:23:33 UTC 
Created attachment 659080 [details]
File: proc_pid_status
Comment 10 Mads Kiilerich 2012-12-06 22:23:35 UTC 
Created attachment 659081 [details]
File: smolt_data
Comment 11 Mads Kiilerich 2012-12-07 00:03:38 UTC 
The problem might have been caused by piping the output of tshark through something ... and breaking that pipe.
Comment 12 Fedora End Of Life 2013-07-04 02:31:02 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.
Comment 13 Fedora End Of Life 2013-08-01 08:32:35 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.