(Tcl) Ftp2 Debug Log File Path
Demonstrates how to use the DebugLogFilePath property to get information if a Chilkat method crashes or hangs.
load ./chilkat.dll
set ftp [new_CkFtp2]
# ...
# ...
# Insert this code just before the method call that crashes or hangs.
CkFtp2_put_VerboseLogging $ftp 1
CkFtp2_put_DebugLogFilePath $ftp "/some/file/path/sftp_debug_log.txt"
# Make the call that crashes or hangs,
# for example, if the method is PutFile:
set remoteFilePath "..."
set localFilePath "..."
set success [CkFtp2_PutFile $ftp $localFilePath $remoteFilePath]
# 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 == 0} then {
puts [CkFtp2_lastErrorText $ftp]
delete_CkFtp2 $ftp
exit
}
delete_CkFtp2 $ftp
|