Thanks for the info. May I ask a follow-up question? Does this error code 79 always occur when the user tries to download a non-existing file from a remote system?
If that is the case, I could change the message text in my program when encountering code 79.

M. Nguyen

From: Daniel Stenberg [mailto:bagder_at_users.sf.net]
Sent: Wednesday, April 16, 2014 3:06 PM
To: [curl:bugs]
Subject: [curl:bugs] #1361 Error code 79


  * labels: --> SCP/SFTP
  * assigned_to: Daniel Stenberg
  * Priority: 5 --> 4
  * Comment:

I don't remember why, but the verbose string is just help for humans to understand the error - we don't guarantee anything and it isn't for machine parsing. I therefore don't consider this a bug, but merely an inconvenience. Yes, I think the more expressive error text was better and I would appreciate a patch for it, but I'll probably not spend much personal effort on this.

________________________________

---
** [bugs:#1361] Error code 79**
**Status:** open
**Labels:** SCP/SFTP 
**Created:** Wed Apr 16, 2014 08:31 PM UTC by Minh Nguyen
**Last Updated:** Wed Apr 16, 2014 10:06 PM UTC
**Owner:** Daniel Stenberg
(I submitted the following to the mailing list but did not get any response, hence this bug).

We currently used libcurl version 7.19.7 with libssh2 version 1.2.2.
Given the typical following code fragment:

-----------------
(…)
CURL* curl;
char errorBuf[1024];
int result;

if (curl_global_init(CURL_GLOBAL_ALL) != CURLE_OK)
   return 0;

curl = curl_easy_init();

(…)
curl_easy_setopt(curl, CURLOPT_ERRORBUFFER, errorBuf);
curl_easy_setopt(curl, CURLOPT_VERBOSE, 1);
(…)

result = curl_easy_perform (curl);
printf(“curl_easy_perform() returned result=%d, msg=%s\n”, result, errorBuf);
---------------

When we tried to download a non-existing file (“/tmp/non-exist.txt”) via scp, we got the correct info for the printf statement:

            “curl_easy_perform() returned result=79, msg=scp: /tmp/non-exist.txt: No such file or directory”


After we upgrade to the latest version of libssh2 (1.4.3), now we got a different error message from libcurl:

             “curl_easy_perform() returned result=79, msg=Failed to recv file”

We upgraded to the latest version of libcurl 7.36.0, but we still got the same error message “Failed to recv file” (instead of “No such file or directory”).

Is it an expected change in the error message string corresponding to error code 79?
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to http://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at http://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.