cURL / Mailing Lists / curl-library / Single Mail


Re: problem with simultaneous sftp connections.

From: michele <>
Date: Thu, 11 Aug 2011 15:29:24 +0200

Hi again,
Unfortunately I cannot change the versions: I'm using libssh2
and libcURL 7.19.7.
(I'm working on RHEL 6 x86_64)

Anyway, just for try, I updated only libssh2 to and I still
encountered again the problem with libssh2:

(gdb) where
#0 0x0000000000000000 in ?? ()
#1 0x00007ffff680fd33 in _libssh2_cipher_crypt (ctx=<value optimized
out>, algo=<value optimized out>, encrypt=<value optimized out>,
block=0x7fff6001f1b0 "")
     at openssl.c:197
#2 0x00007ffff680ccc9 in _libssh2_transport_write
(session=0x7fff6000af50, data=0x7fff60017fc0 "^", data_len=16422) at
#3 0x00007ffff67f9c6c in _libssh2_channel_write
(channel=0x7fff60010430, stream_id=0, buf=0x7fff60013f90 "",
buflen=16413) at channel.c:2014
#4 0x00007ffff680756a in sftp_write (hnd=0x7fff6000fd90,
buffer=0x7fff60005a19 "", count=<value optimized out>) at sftp.c:1432
#5 libssh2_sftp_write (hnd=0x7fff6000fd90, buffer=0x7fff60005a19 "",
count=<value optimized out>) at sftp.c:1486
#6 0x000000306923b4e3 in Curl_sftp_send () from /usr/lib64/
#7 0x0000003069217a65 in Curl_write () from /usr/lib64/
#8 0x000000306922b1c7 in Curl_readwrite () from /usr/lib64/
#9 0x000000306922bca8 in Curl_perform () from /usr/lib64/

If I can demonstrate that the bug disappear with the new versions, then
we can ask to update the two libraries (we are working with external
partners, thus we cannot change the libraries as we want....).

Is it needed to update libCurl too or not ?
...BTW I know that this problem is not related to libCurl (it is clear!)...

Thank you.

On 08/10/2011 07:56 PM, Daniel Stenberg wrote:
> On Wed, 10 Aug 2011, michele wrote:
>> I made the following changes to my program:
>> But the result is the same segfault:
>> (gdb) where
>> #0 0x0000000000000000 in ?? ()
>> #1 0x0000003992a1e883 in ?? () from /usr/lib64/
>> #2 0x0000003992a1c7b9 in ?? () from /usr/lib64/
>> #3 0x0000003992a0591a in ?? () from /usr/lib64/
>> #4 0x0000003992a16475 in libssh2_sftp_write () from
>> /usr/lib64/
> Then I guess the next step is debugging. build a debug version of
> libssh2 as well so that you get proper debug symbols etc. Then when/if
> it crashes, you can use gdb to figure out details. Or run it with
> valgrind and more.
> I forgot to ask, but I trust that you tried with the latest version of
> both libs too so that you're not just experiencing a bug in older
> versions.

ATTENZIONE: le informazioni contenute in questo messaggio sono da considerarsi confidenziali ed il loro utilizzo e' riservato unicamente al destinatario sopra indicato. Chi dovesse ricevere questo messaggio per errore e' tenuto ad informare il mittente ed a rimuoverlo definitivamente da ogni supporto elettronico o cartaceo.

WARNING: This message contains confidential and/or proprietary information which may be subject to privilege or immunity and which is intended for use of its addressee only. Should you receive this message in error, you are kindly requested to inform the sender and to definitively remove it from any paper or electronic format.
List admin:
Received on 2011-08-11