Discussion:
bug (seg fault in Library view)
Viktor Skalák
2011-05-16 01:41:24 UTC
Permalink
Hey,
with fresh installation of cmus I get segmentation fault when hitting the
Enter key in Library view. The Library is blank (there are no tracks added
yet). Some debug info below, hope it helps.

Viktor.

P.S.: I'm new to cmus and love it already, thanks

...
(gdb) step

Program received signal SIGSEGV, Segmentation fault.
tree_set_selected () at tree.c:497
497        info = tree_track_info(lib_cur_track);
(gdb) bt
#0  tree_set_selected () at tree.c:497
#1  0x080555b5 in cmd_win_activate (arg=0x0) at command_mode.c:1442
#3  0x08059577 in run_command (buf=0x8094a84 "win-activate") at
command_mode.c:2748
#3  0x08063b26 in handle_key (b=<value optimized out>, k=<value
optimized out>) at keys.c:578
#4  0x08063f60 in normal_mode_ch (ch=10) at keys.c:625
#5  0x080739b0 in handle_ch (ch=10) at ui_curses.c:1887
#6  0x08075519 in u_getch () at ui_curses.c:1974
#7  main_loop () at ui_curses.c:2083
#8  0x08051381 in main (argc=1, argv=0xbffff7b8) at ui_curses.c:2375
Johannes Weißl
2011-05-16 10:29:34 UTC
Permalink
Hello Viktor,
Post by Viktor Skalák
with fresh installation of cmus I get segmentation fault when hitting the
Enter key in Library view. The Library is blank (there are no tracks added
yet). Some debug info below, hope it helps.
Thanks for the report and the gdb backtrace! I can reproduce the bug, it
was introduced in version 2.4.0 (by me... :-( ). I attached a patch, it
should be fixed in the next version of cmus!


Greetings,
Johannes
Gregory Petrosyan
2011-05-16 12:54:45 UTC
Permalink
Post by Johannes Weißl
Post by Viktor Skalák
with fresh installation of cmus I get segmentation fault when hitting the
Enter key in Library view. The Library is blank (there are no tracks added
yet). Some debug info below, hope it helps.
Thanks for the report and the gdb backtrace! I can reproduce the bug, it
was introduced in version 2.4.0 (by me... :-( ). I attached a patch, it
should be fixed in the next version of cmus!
Merged, thanks for the quick fix! Since this is the first reported major bug in
2.4.0, I think it makes sense to release 2.4.1 in about a week.

Gregory

Loading...