On Sunday, May 14, 2017, 19:46:45, Darshit Shah wrote: > Then could you please provide us with a command line that sometimes > crashes and preferably the debug output from Wget when it crashes. Not the > debugger, but just the debug.
I use either wget -t0 -c -S <url> or wget -t0 -c -S --trust-server-names <url> Seems to happen more often with larger files. I don't remember any special output when the crash happens - just the standard progress bar, and Windows' crash notification. > I would like to reduce it to some kind of a minimal test case. Maybe the > progress bar routines are crashing, or maybe it is something to do with how > we access the filesystem, or something entirely different. I thought about the progress bar, since it does behave a bit weird on Windows - specifically, if the filename is scrolling, once it starts off-screen, the last letter keeps getting repeated, while the rest of the progress bar stops updating, however the crashes seem to happen regardless of how the filename is displayed. > However, since you say you can't reproduce it inside a debugger, I would > hazard a guess that the issue lies somewhere in using uninitialized memory. > The debugger will initialize the memory and hence prevent some class of > bugs from occurring. An audit of the WIndows-specific code might be in > order for this since I haven't heard of such an issue on *nix machines. The annoying thing is that I haven't even had a crash since I set up DrMingw as just-in-time debugger (debugger that Windows invokes only when a crash occurs, and which otherwise isn't running). The last time my build crashed for me was about a month ago, downloading some ISO file at work, while I hadn't had it crash on my home computer in well over a year (I even tried setting up a batch file that just ran wget in a loop and leaving it in the background, but it wouldn't crash). -- < Jernej Simončič ><><><><>< http://eternallybored.org/ > The bus that left the stop just before you got there is your bus. -- First Law of Bus Transportation