Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#31320 - [tmux] crashes on certain keys
Attached to Project:
Community Packages
Opened by Andreas (misc) - Tuesday, 28 August 2012, 15:57 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 13 October 2012, 15:49 GMT
Opened by Andreas (misc) - Tuesday, 28 August 2012, 15:57 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 13 October 2012, 15:49 GMT
|
DetailsDescription:
Like the title says, libevent 2.0.20 has my tmux (the whole server) crash instantly with SIGSEGV on pressing keys like Alt-[any other] and Esc. Recompiling tmux and libevent did not help, but downgrading to 2.0.19 has it stable again. Additional info: * package version(s): 2.0.19: OK, 2.0.20: fail #0 0x00007f3a69647229 in event_pending () from /lib/libevent-2.0.so.5 #1 0x000000000043e92f in tty_keys_next (tty=0x15bc338) at tty-keys.c:546 #2 0x00000000004401e1 in tty_read_callback (bufev=0x15c8d90, data=0x15bc338) at tty.c:177 #3 0x00007f3a6965432a in ?? () from /lib/libevent-2.0.so.5 #4 0x00007f3a69649944 in event_base_loop () from /lib/libevent-2.0.so.5 #5 0x0000000000433860 in server_loop () at server.c:212 #6 0x0000000000433844 in server_start (lockfd=6, lockfile=0x1592050 "") at server.c:203 #7 0x0000000000404cbd in client_connect (path=0x68b700 <socket_path> "/tmp/tmux-1000/default", start_server=1) at client.c:124 #8 0x0000000000404f64 in client_main (argc=4, argv=0x7fff12378e50, flags=1) at client.c:220 #9 0x000000000043e0d2 in main (argc=4, argv=0x7fff12378e50) at tmux.c:404 Steps to reproduce: 1. install libevent 2.0.20 2. start tmux 3. press eg. Esc |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Saturday, 13 October 2012, 15:49 GMT
Reason for closing: Fixed
Additional comments about closing: tmux 1.7-1
Saturday, 13 October 2012, 15:49 GMT
Reason for closing: Fixed
Additional comments about closing: tmux 1.7-1
0x00007feeccf5cfb7 in event_pending (ev=0x1be53f8, event=1, tv=0x0) at event.c:1849
1849 EVBASE_ACQUIRE_LOCK(ev->ev_base, th_base_lock);
(gdb) bt
#0 0x00007feeccf5cfb7 in event_pending (ev=0x1be53f8, event=1, tv=0x0) at event.c:1849
#1 0x000000000043e92f in tty_keys_next (tty=0x1be5338) at tty-keys.c:546
#2 0x00000000004401e1 in tty_read_callback (bufev=0x1bf1d90, data=0x1be5338) at tty.c:177
#3 0x00007feeccf68872 in _bufferevent_run_readcb (bufev=bufev@entry=0x1bf1d90) at bufferevent.c:232
#4 0x00007feeccf69a26 in bufferevent_readcb (fd=6, event=<optimized out>, arg=0x1bf1d90) at bufferevent_sock.c:183
#5 0x00007feeccf602c5 in event_persist_closure (ev=0x1bf1da0, base=0x1bba720) at event.c:1297
#6 event_process_active_single_queue (activeq=0x1bba6e0, base=0x1bba720) at event.c:1341
#7 event_process_active (base=<optimized out>) at event.c:1416
#8 event_base_loop (base=0x1bba720, flags=1) at event.c:1617
#9 0x00007feeccf605b9 in event_loop (flags=<optimized out>) at event.c:1529
#10 0x0000000000433860 in server_loop () at server.c:212
#11 0x0000000000433844 in server_start (lockfd=6, lockfile=0x1bbb050 "") at server.c:203
#12 0x0000000000404cbd in client_connect (path=0x68b700 <socket_path> "/tmp/tmux-1000/default", start_server=1) at client.c:124
#13 0x0000000000404f64 in client_main (argc=4, argv=0x7fff1286a830, flags=1) at client.c:220
#14 0x000000000043e0d2 in main (argc=4, argv=0x7fff1286a830) at tmux.c:404
https://sourceforge.net/tracker/?func=detail&aid=3562481&group_id=50884&atid=461322
Following his advise, I posted a small patch on the tmux bugtracker: https://sourceforge.net/tracker/?func=detail&aid=3562489&group_id=200378&atid=973262
No crashes so far anymore.
doesn't apply flawlessly on 1.6 sources -- I'll backport it, but it would be waste
of time if in the coming days there will be new release.