Bug 1098737

Summary: [abrt] tmux: __tsearch(): tmux killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Florian Kisser <fedoraproject>
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, fedoraproject, praiskup, psabata, rosset.filipe, strobert, sven
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2eade8ae9932f07daf9e82ed0dc12c842501511a
Whiteboard: abrt_hash:b50d46c2b4010c6f39a50e9daaaa8ab9d8b7c3e6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-31 23:51:12 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 Florian Kisser 2014-05-17 20:06:37 UTC 
Description of problem:
I used tmux as byobu backend. Two things were running in tmux when it crashed:

 * bash and journalctl -f
 * bash and btrfs scrub in foreground of a backup drive
 * several other bashes were idling

The scrub kept running in background for some time and finished without an error.

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

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        tmux -2 -f /usr/share/byobu/profiles/tmuxrc new-session -n - /usr/bin/byobu-shell
crash_function: __tsearch
executable:     /usr/bin/tmux
kernel:         3.14.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 __tsearch at tsearch.c:280
 #7 __add_to_environ at setenv.c:212
 #8 __setenv at setenv.c:307
 #9 environ_push at environ.c:176
 #10 job_run at job.c:66
 #11 status_find_job at status.c:535
 #12 status_replace1 at status.c:386
 #13 status_replace at status.c:470
 #14 status_redraw_get_right at status.c:108
 #15 status_redraw at status.c:183
Comment 1 Florian Kisser 2014-05-17 20:06:43 UTC 
Created attachment 896671 [details]
File: backtrace
Comment 2 Florian Kisser 2014-05-17 20:06:46 UTC 
Created attachment 896672 [details]
File: cgroup
Comment 3 Florian Kisser 2014-05-17 20:06:50 UTC 
Created attachment 896673 [details]
File: core_backtrace
Comment 4 Florian Kisser 2014-05-17 20:06:52 UTC 
Created attachment 896674 [details]
File: dso_list
Comment 5 Florian Kisser 2014-05-17 20:06:54 UTC 
Created attachment 896675 [details]
File: environ
Comment 6 Florian Kisser 2014-05-17 20:06:56 UTC 
Created attachment 896676 [details]
File: exploitable
Comment 7 Florian Kisser 2014-05-17 20:06:58 UTC 
Created attachment 896677 [details]
File: limits
Comment 8 Florian Kisser 2014-05-17 20:07:01 UTC 
Created attachment 896678 [details]
File: maps
Comment 9 Florian Kisser 2014-05-17 20:07:03 UTC 
Created attachment 896679 [details]
File: open_fds
Comment 10 Florian Kisser 2014-05-17 20:07:05 UTC 
Created attachment 896680 [details]
File: proc_pid_status
Comment 11 Florian Kisser 2014-05-17 20:07:07 UTC 
Created attachment 896681 [details]
File: var_log_messages
Comment 12 Filipe Rosset 2014-05-31 20:12:11 UTC 
Hi Florian, are you able to reproduce the issue (ex, following a test case)? I'm asking it because I need a way to reproduce the issue, before report it to upstream, otherwise they'll close the bug.
Comment 13 Florian Kisser 2014-05-31 22:31:43 UTC 
Hi Filipe, thank you for your answer! I fear I wasn't able to reproduce it, so I think it's better to close it for now and maybe reopen if somebody can.