links consistently segfault on https://github.com/numba/llvmlite/ $ gdb -q --args links https://github.com/numba/llvmlite/ (…) (gdb) r (…) Program received signal SIGSEGV, Segmentation fault. 0x000000000048abe0 in update_assoc () (gdb) bt #0 0x000000000048abe0 in update_assoc () #1 0x000000000041e8d8 in type_rd () #2 0x000000000041eefa in load_config_file () #3 0x0000000000420054 in load_config () #4 0x000000000046696e in init () #5 0x0000000000478ec9 in select_loop () #6 0x000000000040756f in main ()
Links upstream says if you find a bug: Send bugreport to the following four addresses: mikulas at twibright.com brain at twibright.com clock at twibright.com perm at twibright.com Bugreport should include how to invoke the bug, what version you have got, what operation system do you run Links, and if you know it, then also what capabilities have been compiled in Links. If Links segfaults, then look if you got the core. If not, switch the coredump on with "ulimit -c unlimited" and segault links with the bug one more time. Then archive the core. Do not send the core as an attachment.
Well, it's a downstream issue. The same version works fine on Fedora…
Humm interestingly it works with some local accounts and not with others…
It happens when parsing ~/.links/links.cfg…
OK, for any accounts, links will segfault on any site, providing you: * save settings (<esp>, then <Esp> Setup>Langage>French) * quit * restart links Whatever the langage is (tested with both English & French) The same works fine on eg Fedora
Disabling patch 23 (links-2.15-dont-have-two-assocations-with-same-label--otherwise-one-cant-override-shared-config.patch) fixes that… This one is a very old one: * Sat Oct 08 2005 Pixel <pixel@mandriva.com> 2.1-0.pre18.6mdk - don't have two assocations with same label, otherwise one can't override shared config
links-2.14-1.mga6 was good links-2.19-1.mga7 was broken There's nothing standing out in the 2.15 rediff but I'll dig further…
Summary: links consistently segfault on https://github.com/numba/llvmlite/ => links consistently segfault on any site once its configuration has been saved once
Patch disabled for now
Status: NEW => RESOLVEDResolution: (none) => FIXED