Bug 1086851

Summary: [abrt] tmux: evbuffer_chain_insert(): tmux killed by SIGSEGV
Product: [Fedora] Fedora Reporter: kianby
Component: tmuxAssignee: Sven Lankes <sven>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcantrell, kianby, praiskup, psabata, rosset.filipe, strobert, sven
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e21e655db4696b277ae5b4df77a8ee53bb1b3db9
Whiteboard: abrt_hash:58f2f08c2f2c4a549c4aab9105d9a29909282894
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-31 20:12:59 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description kianby 2014-04-11 16:38:16 UTC 
Description of problem:
Crash on Tmux session exit

Version-Release number of selected component:
tmux-1.9a-2.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        tmux
crash_function: evbuffer_chain_insert
executable:     /usr/bin/tmux
kernel:         3.13.9-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 evbuffer_chain_insert at buffer.c:295
 #1 evbuffer_add at buffer.c:1608
 #2 bufferevent_write at bufferevent.c:379
 #3 tty_puts at tty.c:402
 #5 tty_putcode at tty.c:364
 #6 tty_start_tty at tty.c:208
 #7 server_client_msg_dispatch at server-client.c:881
 #8 server_client_callback at server-client.c:235
 #9 event_process_active_single_queue at event.c:1350
 #10 event_process_active at event.c:1420
Comment 1 kianby 2014-04-11 16:38:28 UTC 
Created attachment 885479 [details]
File: backtrace
Comment 2 kianby 2014-04-11 16:38:33 UTC 
Created attachment 885480 [details]
File: cgroup
Comment 3 kianby 2014-04-11 16:38:39 UTC 
Created attachment 885481 [details]
File: core_backtrace
Comment 4 kianby 2014-04-11 16:38:44 UTC 
Created attachment 885482 [details]
File: dso_list
Comment 5 kianby 2014-04-11 16:38:51 UTC 
Created attachment 885483 [details]
File: environ
Comment 6 kianby 2014-04-11 16:38:57 UTC 
Created attachment 885484 [details]
File: exploitable
Comment 7 kianby 2014-04-11 16:39:00 UTC 
Created attachment 885485 [details]
File: limits
Comment 8 kianby 2014-04-11 16:39:04 UTC 
Created attachment 885486 [details]
File: maps
Comment 9 kianby 2014-04-11 16:39:07 UTC 
Created attachment 885487 [details]
File: open_fds
Comment 10 kianby 2014-04-11 16:39:11 UTC 
Created attachment 885488 [details]
File: proc_pid_status
Comment 11 kianby 2014-04-11 16:39:14 UTC 
Created attachment 885489 [details]
File: var_log_messages
Comment 12 Filipe Rosset 2014-05-21 21:53:37 UTC 
Are you able to reproduce the issue? I need a test case to reproduce the issue, prior to file a bug with upstream, otherwise they will not work on it.
Comment 13 kianby 2014-05-22 14:43:15 UTC 
(In reply to Filipe Rosset from comment #12)
> Are you able to reproduce the issue? I need a test case to reproduce the
> issue, prior to file a bug with upstream, otherwise they will not work on it.

It happened one time only. I'm afraid I can't provide any clue.