Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: wget-1.14-3.fc18 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: wget -nc -i /home/federico/et.txt crash_function: retrieve_url executable: /usr/bin/wget kernel: 3.9.6-200.fc18.i686.PAE runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (2 frames) #1 retrieve_url at retr.c:840 #2 retrieve_from_file at retr.c:1075
Created attachment 774967 [details] File: backtrace
Created attachment 774968 [details] File: cgroup
Created attachment 774969 [details] File: core_backtrace
Created attachment 774970 [details] File: dso_list
Created attachment 774971 [details] File: environ
Created attachment 774972 [details] File: limits
Created attachment 774973 [details] File: maps
Created attachment 774974 [details] File: open_fds
Created attachment 774975 [details] File: proc_pid_status
Created attachment 774976 [details] File: var_log_messages
Hi. Can you please attach also the /home/federico/et.txt file? So I can reproduce the bug and also test it if fixed. Thanks!
Thanks for the answer. You obviously were going to need it but forgot to attach and now it's on another machine I don't have access to for a while. The problem was caused by some lines consisting in URLs with special characters e.g. http://etherpad.wikimedia.org/wmukhack11Lør or http://etherpad.wikimedia.org/wmukhack11Søn , removing such lines let wget continue till the end. The actual URL was actually weirder than that, e.g. http://web.archive.org/web/*/http://etherpad.wikimedia.org/wmukhack11Søn which seem to cause a loop. I probably shouldn't input such URLs in the first place, perhaps wget might want to avoid dying so abruptly on them though.
From what I tested and investigated, the issue should be fixed by fixing Bug #981778. I was not able to reproduce it with the latest wget version, but with the older version (wget-1.14-3.fc18) I was. Please update your wget to the latest version (wget-1.14-5.fc18) if you didn't do so. If you encounter this issue in the future, feel free to reopen this Bug of open a new one. *** This bug has been marked as a duplicate of bug 981778 ***