Bug 1069950

Summary:	tmux 1.9a instantly segfaults with MALLOC_CHECK_=2
Product:	[Fedora] Fedora	Reporter:	Dave Jones <davej>
Component:	tmux	Assignee:	Sven Lankes <sven>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	davej, dcantrell, pfrields, praiskup, psabata, rosset.filipe, strobert, sven
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tmux-1.9a-2.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-04 06:42:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave Jones 2014-02-26 00:37:24 UTC

Reading symbols from /usr/bin/tmux...Reading symbols from /usr/lib/debug/usr/bin/tmux.debug...done.
done.
[New LWP 25730]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `tmux'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007f7eec379c39 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install glibc-2.18-12.fc20.x86_64 libevent-2.0.21-3.fc20.x86_64 ncurses-libs-5.9-12.20130511.fc20.x86_64
(gdb) bt
#0  0x00007f7eec379c39 in raise () from /lib64/libc.so.6
#1  0x00007f7eec37b348 in abort () from /lib64/libc.so.6
#2  0x00007f7eec3c193b in free_check () from /lib64/libc.so.6
#3  0x0000000000405f52 in client_main (argc=argc@entry=0, argv=argv@entry=0x7fffba77b090, flags=flags@entry=65536) at client.c:308
#4  0x0000000000403bd5 in main (argc=0, argv=0x7fffba77b090) at tmux.c:389

Comment 1 Filipe Rosset 2014-02-26 00:48:15 UTC

Hi Dave, I'm unable to reproduce this issue here, everything fine in F20 fully updated, glibc, libevent and ncurses/ncurses-lib are the same of your stack trace.

Do you have any special steps to reproduce this issue?

Comment 2 Filipe Rosset 2014-02-26 00:56:04 UTC

It's also working fine on rawhide-x86_64.

Could be related:
https://bugzilla.redhat.com/show_bug.cgi?id=1030719

Comment 3 Filipe Rosset 2014-02-26 03:01:07 UTC

OK, I can confirm the issue in Fedora builds and also in a compiled tmux over Ubuntu 13.10, so I reported the issue to tmux upstream. Thanks Dave.

https://sourceforge.net/p/tmux/tickets/105/

Comment 4 Fedora Update System 2014-02-26 13:30:03 UTC

tmux-1.9a-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/tmux-1.9a-2.fc20

Comment 5 Fedora Update System 2014-02-26 13:41:34 UTC

tmux-1.9a-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/tmux-1.9a-2.fc19

Comment 6 Fedora Update System 2014-02-28 18:26:49 UTC

Package tmux-1.9a-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tmux-1.9a-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-3161/tmux-1.9a-2.fc20
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2014-03-04 06:42:56 UTC

tmux-1.9a-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.