(Unicode C) SFTP Debug Log File Path

Demonstrates how to use the DebugLogFilePath property to get information if a Chilkat method crashes or hangs.

Chilkat C/C++ Library Downloads
MS Visual C/C++ Linux/CentOS C/C++ Alpine Linux C/C++ MAC OS X C/C++	armhf/aarch64 C/C++ C++ Builder iOS C/C++ Android C/C++	Solaris C/C++ MinGW C/C++

#include <C_CkSFtpW.h>

void ChilkatSample(void)
    {
    HCkSFtpW sftp;
    const wchar_t *remoteFilePath;
    const wchar_t *localFilePath;
    BOOL success;

    sftp = CkSFtpW_Create();

    // Insert this code just before the method call that crashes or hangs.
    CkSFtpW_putVerboseLogging(sftp,TRUE);
    CkSFtpW_putDebugLogFilePath(sftp,L"/some/file/path/sftp_debug_log.txt");

    // Make the call that crashes or hangs,
    // for example, if the method is DownloadFileByName:

    remoteFilePath = L"...";
    localFilePath = L"...";
    success = CkSFtpW_DownloadFileByName(sftp,remoteFilePath,localFilePath);

    // Note: If the method returns control to your application code, then it did not crash within Chilkat.
    // The DebugLogFilePath property causes all information that would be recorded in the LastErrorText to be emitted to the
    // log file (with immediate file write flushing, i.e. no buffering).  Thus, in a crash situation,
    // the log file will contain information up to the point of the crash.

    if (success == FALSE) {
        wprintf(L"%s\n",CkSFtpW_lastErrorText(sftp));
        CkSFtpW_Dispose(sftp);
        return;
    }



    CkSFtpW_Dispose(sftp);

    }