shinys000114/libssh
1
0
Fork 0
mirror of https://git.libssh.org/projects/libssh.git synced 2026-02-11 02:38:09 +09:00
Code Issues Packages Projects Releases Wiki Activity

doc: clarify tutorial error section

Browse Source 
Signed-off-by: Davide "FunkyAss" Del Zompo <davide.delzompo@gmail.com>
Reviewed-by: Andreas Schneider <asn@cryptomilk.org>
This commit is contained in:
Davide \"FunkyAss\" Del Zompo
2014-12-01 19:33:27 +01:00
committed by Andreas Schneider
parent 03095f1516
commit bb197de75d
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/guided_tour.dox
View File

@@ -443,11 +443,10 @@ Most of time, the error returned are SSH_FATAL, but some functions
(generaly the ssh_request_xxx ones) may fail because of server denying request. (generaly the ssh_request_xxx ones) may fail because of server denying request.
In these cases, SSH_REQUEST_DENIED is returned. In these cases, SSH_REQUEST_DENIED is returned.
ssh_get_error() and ssh_get_error_code() take a ssh_session as a parameter. For thread safety, errors are bound to ssh_session objects.
That's for thread safety, error messages that can be attached to a session As long as your ssh_session object is not NULL, you can retrieve the last error
aren't static anymore. Any error that happens during ssh_options_xxx() message and error code from the ssh_session using ssh_get_error() and
or ssh_connect() (i.e., outside of any session) can be retrieved by ssh_get_error_code() respectively.
giving NULL as argument.
The SFTP subsystem has its own error codes, in addition to libssh ones. The SFTP subsystem has its own error codes, in addition to libssh ones.