After several transfers, both up and down, ascii and binary file types
(though all are downloaded in binary mode), I can occasionally get the
following error:
debug3- Data connection established
debug3> RETR 00md5sums
debug3-<--- 150 Opening BINARY mode data connection for 00md5sums (19922
On Mon, Oct 17, 2005 at 01:27:38AM -0600, Archaic wrote:
>
> *** glibc detected *** double free or corruption (!prev): 0x0817e740 ***
3.3.2 seems to have cleared this up.
--
Archaic
Want control, education, and security from your operating system?
Hardened Linux From Scratch
http://www.linuxfr
> > The below patch fixes this by restarted the Schedule() loop if we've
> > deleted anything and were not at the end of the chain. (It also
> > protects the delete call against being called on 0x0, but that might
> > be a usual idiom in C++.)
Thanks for the patch. I have used a different approach
Hello Alexander,
here a patch from Paul for the reported double free problem:
Weitergeleitete Nachricht
> Von: Paul TBBle Hampson <[EMAIL PROTECTED]>
> Betreff: Bug#334292: Solution to lftp double-free-on-put
> The double-free in lftp is caused by the SMTask::Schedule's deleti
lftp is giving errors on two different systems. The error seems to
always happen during or at the end of a file transfer. It's never
happened with ls or cd. A couple of times it happened during logging in.
Both systems have glibc-2.3.4 w/nptl, gcc-3.4.3. One system uses
openssl-0.9.7e, the other u
