> -----Original Message----- > From: libssh2-devel-boun...@cool.haxx.se > [mailto:libssh2-devel-boun...@cool.haxx.se] On Behalf Of > Daniel Stenberg > Sent: Wednesday, September 16, 2009 4:38 PM > To: libssh2 development > Subject: RE: libss2 debug level > > Then you don't use a libssh2 version built with debug > enabled. configure --enable-debug is your friend!
Yes, I forgot to use this flag to configure it. Thanks for reminding. Now I get a lot of information, most of them binary. So I think ~0 is not a good idea. Instead, I set the trace flag to be LIBSSH2_TRACE_ERROR now. Here is the trace: =================================================== q...@durian(pts/2):~/opensrc/libssh2-1.2/example/simple[145]$ ./sftp 13.198.98.190 qxu fair123 [libssh2] 0.178181 Failure Event: -37 - Would block waiting for banner [libssh2] 0.186328 Failure Event: -37 - Would block exchanging encryption keys [libssh2] 0.192722 Failure Event: -37 - Would block exchanging encryption keys Fingerprint: 0B F2 D3 94 9D 0F 75 BE 69 15 33 42 B8 0D 88 CA [libssh2] 0.268435 Failure Event: -37 - Would block requesting userauth list Authentication methods: publickey,gssapi-with-mic,password libssh2_sftp_init()! [libssh2] 0.276924 Failure Event: -37 - Would block [libssh2] 0.276947 Failure Event: -37 - Would block starting up channel [libssh2] 0.292252 Failure Event: -37 - Would block to request SFTP subsystem [libssh2] 0.327202 Failure Event: -25 - SFTP packet too large [libssh2] 0.327250 Failure Event: -30 - Timeout waiting for response from SFTP subsystem Unable to init SFTP session all done =================================================== There are so many "Failure event". Which one is the most critical? Thanks, Xu Qiang _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
