Chilkat HOME .NET Core C# Android™ AutoIt C C# C++ Chilkat2-Python CkPython Classic ASP DataFlex Delphi ActiveX Delphi DLL Go Java Lianja Mono C# Node.js Objective-C PHP ActiveX PHP Extension Perl PowerBuilder PowerShell PureBasic Ruby SQL Server Swift 2 Swift 3,4,5... Tcl Unicode C Unicode C++ VB.NET VBScript Visual Basic 6.0 Visual FoxPro Xojo Plugin
(Visual FoxPro) Ftp2 Debug Log File PathDemonstrates how to use the DebugLogFilePath property to get information if a Chilkat method crashes or hangs.
LOCAL loFtp LOCAL lcRemoteFilePath LOCAL lcLocalFilePath LOCAL lnSuccess * For versions of Chilkat < 10.0.0, use CreateObject('Chilkat_9_5_0.Ftp2') loFtp = CreateObject('Chilkat.Ftp2') * ... * ... * Insert this code just before the method call that crashes or hangs. loFtp.VerboseLogging = 1 loFtp.DebugLogFilePath = "/some/file/path/sftp_debug_log.txt" * Make the call that crashes or hangs, * for example, if the method is PutFile: lcRemoteFilePath = "..." lcLocalFilePath = "..." lnSuccess = loFtp.PutFile(lcLocalFilePath,lcRemoteFilePath) * 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 (lnSuccess = 0) THEN ? loFtp.LastErrorText RELEASE loFtp CANCEL ENDIF RELEASE loFtp |
© 2000-2024 Chilkat Software, Inc. All Rights Reserved.