Summary: | app-misc/vifm-0.5 segfaults with ncurses-5.8 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nikolaj Šujskij <skrattaren> |
Component: | Current packages | Assignee: | Alex Alexander (RETIRED) <wired> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ViFM/ncurses 5.8 crash backtrace |
Description
Nikolaj Šujskij
2011-03-16 15:51:12 UTC
Which version of ncurses? Could you provide a gdb backtrace? (In reply to comment #1) > Which version of ncurses? sys-libs/ncurses-5.8 > Could you provide a gdb backtrace? I suppose I could, but it'd take time, since I'm not that much into debugging. Does it work for you? Not just amd64. I run ~x86 and vifm broke when I emerged ncurses-5.8. It has worked fine with all previous ncurses. Going back to ncurses-5.7-r6 fixed it. ViFM dies on line 701 of keys.c which is the first call to redrawwin(lwin,title). Thanks, Dave Day PS This is my first interaction with a bugzilla type thing so I have yet to learn what other stuff I am supposed to do. I'll figure that out and comeback. Indeed, downgrading ncurses fixes the issue. Maybe, description should be changed to "app-misc/vifm-0.5 segfaults with sys-libs/ncurses-5.8"? Seems like I cannot do it myself. Here's backtrace attached, but it's not that more informative than Dave's message. Maybe I missed something in our "Get meaningful backtraces" guide, in that case please let me know. Created attachment 266441 [details]
ViFM/ncurses 5.8 crash backtrace
This was indeed an issue with ncurses-5.8. I've added a patch (got it from the arch package) in vifm-0.5-r1 that fixes the issue. Thanks for reporting :) |