Date: Sat, 19 Feb 2011 12:55:09 GMT From: Jason Mann <jason.mann@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/154883: tmux stops responding, then panics system when kill -9'd Message-ID: <201102191255.p1JCt9RM015460@red.freebsd.org> Resent-Message-ID: <201102191300.p1JD0Ujf044056@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 154883 >Category: ports >Synopsis: tmux stops responding, then panics system when kill -9'd >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 19 13:00:30 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Jason Mann >Release: FreeBSD 8.1-RELEASE-p2 >Organization: >Environment: FreeBSD beastie.b0rken.org 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: When attempting to attach to a detached tmux session using 'tmux attach', the client process will fail to respond, neither attaching to the session or returning to the shell. CTRL+C then has no effect. Once this occurs, any further attempts to attach to the same session from different terminals all do the same thing. If the tmux server process is then killed with the SIGKILL signal, the host panics and reboots. I tried trussing the 'tmux attach' command and noticed some interrupted system calls before the output stopped, but I failed to log this to a file on this occasion. I will log this next time, along with a truss of the server process while the attach is attempted, but it could be days or weeks before this occurs again. Port versions: tmux-1.4_2 libevent-1.4.14b_1 >How-To-Repeat: Start a tmux session and detach from it. Later, attempt to reattach to the session. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201102191255.p1JCt9RM015460>