Hrvoje Niksic <[EMAIL PROTECTED]> writes:
> Herold Heiko <[EMAIL PROTECTED]> writes:
>
> > Some hours and about 1.7M of logfile (with -v) later I got
> >
> > ==> SYST ... done. ==> PWD ... wget: strdup: Not enough memory.
> >
> > The machine definitively had still lots of memory free (at least
> > 50MB).
>
> It might be a memory corruption bug that causes such a message. It
> might be useful to compile Wget with a memory debugger and check
> things. Unfortunately, I haven't found a memory debugger I could
> use, after my last trial Purify license (for Solaris) expired.
Thanks to Drazen, I've now run several huge stress tests of Wget under
dbx's access and leaks checking, and no errors were detected. I tried
to simulate your environment by creating directories with huge names.
Nothing helped; Wget ran flawlessly and still no errors detected.
So I have to conclude that it's either a problem with your system, or
a genuine lack of memory, or a really well hidden Wget problem that I
was unable to tickle.
