On Montag, 15. Mai 2017 13:53:54 CEST Darshit Shah wrote: > Follow-up Comment #1, bug #51029 (project wget): > > Hi, > > Thanks for the bug report! > Could you please also share the entire logs for these runs if you have them > available? Attaching them to the report will be the best way. > > I tried running the command line you provided on my Arch Linux system > against the latest git master and it completed successfully:
I could reproduce the crash with latest Debian unstable (wget 1.19.1), sadly no debug symbols were available and I had to get my train. I'll try later with commit tag 1.19.1 and debug symbols. Regards, Tim > > ``` > FINISHED --2017-05-15 19:42:29-- > Total wall clock time: 4m 31s > Downloaded: 1183 files, 73M in 13s (5.64 MB/s) > ``` > > Since I am unable to reproduce this issue locally, I'm going to need some > help from your end. A --debug trace of when wget crashes will be useful. > Even better would be if you could provide a stack trace by building wget > locally with debug symbols and running it inside gdb. Once it segfauls, you > can type "b" on the command line and get a stack trace. > > Also, could you please test it with the latest git master? It may have been > fixed in the meantime. > > I'm unable to make a guess as to why this occurs. The first guess would be a > race condition, but we don't have any threads in Wget, so that is out of > the question. > > _______________________________________________________ > > Reply to this item at: > > <http://savannah.gnu.org/bugs/?51029> > > _______________________________________________ > Message sent via/by Savannah > http://savannah.gnu.org/
signature.asc
Description: This is a digitally signed message part.
