(AutoIt) Ftp2 Debug Log File Path

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

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

$oFtp = ObjCreate("Chilkat.Ftp2")

; ...
; ...

; Insert this code just before the method call that crashes or hangs.
$oFtp.VerboseLogging = True
$oFtp.DebugLogFilePath = "/some/file/path/sftp_debug_log.txt"

; Make the call that crashes or hangs,
; for example, if the method is PutFile:

Local $sRemoteFilePath = "..."
Local $sLocalFilePath = "..."
Local $bSuccess = $oFtp.PutFile($sLocalFilePath,$sRemoteFilePath)

; 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 ($bSuccess = False) Then
    ConsoleWrite($oFtp.LastErrorText & @CRLF)
    Exit
EndIf