Description of problem: seems to be related to re-starting after a crash or disconnect maybe? Version-Release number of selected component: elinks-0.12-0.35.pre6.fc19 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: links crash_function: get_opt_rec executable: /usr/bin/elinks kernel: 3.12.9-201.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 get_opt_rec at options.c:200 #1 get_opt_ at options.c:288 #2 get_terminal_codepage at terminal.c:121 #3 bookmark_terminal at bookmarks.c:579 #4 bookmark_all_terminals at bookmarks.c:622 #5 bookmark_snapshot at bookmarks.c:712 #6 bookmark_write_hook at bookmarks.c:116 #7 trigger_event_va at event.c:166 #8 trigger_event at event.c:179 #9 periodic_save_handler at timer.c:35
Created attachment 873332 [details] File: backtrace
Created attachment 873333 [details] File: cgroup
Created attachment 873334 [details] File: core_backtrace
Created attachment 873335 [details] File: dso_list
Created attachment 873336 [details] File: environ
Created attachment 873337 [details] File: exploitable
Created attachment 873338 [details] File: limits
Created attachment 873339 [details] File: maps
Created attachment 873340 [details] File: open_fds
Created attachment 873341 [details] File: proc_pid_status
Created attachment 873342 [details] File: var_log_messages
Thank you for the bug report! Is this reproducible? I have a patch candidate that needs to be tested: --- a/src/util/lists.h +++ b/src/util/lists.h @@ -146,7 +146,8 @@ do { \ #define list_empty(x) (list_magic_chkbool(x, "list_empty") && (x).next == &(x)) #define list_is_singleton(x) \ - (list_magic_chkbool(x, "list_is_singleton") && (x).next == (x).prev) + (list_magic_chkbool(x, "list_is_singleton") && (x).next == (x).prev \ + && !list_empty(x)) #define list_has_prev(l,p) \ (list_magic_chkbool(l, "list_has_prev") && (p)->prev != (void *) &(l))
proposed upstream: http://thread.gmane.org/gmane.comp.web.elinks/3570
Sorry, I hadn't noticed your feedback. I'm not sure if the precise bug is reproducible; I know elinks crashes a lot when quitting or when the terminal session (e.g. ssh) is disconnected, but I often don't see the ABRT catches for a day or two back on the console...
Thanks for the info! I will submit updates with the patch above. Please give it a try once it appears in testing.
fixed in elinks-0.12-0.38.pre6.fc21
elinks-0.12-0.36.pre6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/elinks-0.12-0.36.pre6.fc19
elinks-0.12-0.37.pre6.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/elinks-0.12-0.37.pre6.fc20
Package elinks-0.12-0.36.pre6.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing elinks-0.12-0.36.pre6.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-5774/elinks-0.12-0.36.pre6.fc19 then log in and leave karma (feedback).
elinks-0.12-0.36.pre6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
elinks-0.12-0.37.pre6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.