On Thu, 12 Jan 2012, michele.mazzei_at_acsys.it wrote:

> I must move very large files across the intranet; I'm trying to put and get a
> file of 8 gigabytes using sftp.

> For get: I got the following coredump:
>
> (gdb) where
> #0 libssh2_session_block_directions (session=0x0) at session.c:1642
> #1 0x000000366e63dc74 in ssh_block2waitfor (conn=0xee9810, block=<value
> optimized out>) at ssh.c:2310

> OS: CentOS kernel: 2.6.32-131.12.1.el6.x86_64
> cURL:libcurl/7.19.7 zlib/1.2.3 libidn/1.18 libssh2/1.2.7 libgcrypt-1.4.5-3

Does it always happen on this big files or is it bound to this particular
file/server?

Can you please try with a more recent libcurl and libssh2 and see if the bug
persists?

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html