Sample code for 30+ languages & platforms
Java

Using DebugLogFilePath to Debug a Crash

If a crash is suspected to occur within a Chilkat method call, it can be debugged using the VerboseLogging and DebugLogFilePath as shown here.

Chilkat Java Downloads

Chilkat2 Java
import com.chilkatsoft.chilkat2.Crypt2;

public class ChilkatExample {

    public static void main(String[] args) {
        // If a crash is suspected to occur within a Chilkat method call, it can be debugged using the VerboseLogging and DebugLogFilePath as shown here.
        //
        // NOTE: The same technique applies for any Chilkat class that has the DebugLogFilePath property.
        // Most Chilkat classes have DebugLogFilePath.

        Crypt2 crypt = new Crypt2();

        // First make sure VerboseLogging is turned on.
        crypt.setVerboseLogging(true);

        // Set the DebugLogFilePath to the path of a log file that will be created automatically.
        // If the file already exists, Chilkat will append to it.
        crypt.setDebugLogFilePath("c:/someDir/debugLog.txt");

        // Reproduce the problem.

        // ...
        crypt.verifyP7M("c:/someDir/someFile.p7m", "c:/someDir/someFile.dat");
        // ...

        // If a crash occurred within Chilkat, then the debugLog.txt will contain information that
        // can be sent to support@chilkatsoft.com

        // ------------------------------------------------------------------------------------------------
        // Note: Given that the debug log file is always appended, the log file might grow
        // to a very large size.  You can prevent the continual growth of the log file by
        // deleting the log file at certain points, such as after a Chilkat method returns.
        //
        // Given that we're only interested in the log file for Chilkat calls that crash or hang,
        // it's OK to delete the log file after a Chilkat method that returns.
        //
        // The next call to a Chilkat method will re-create the log file.  If the Chilkat call crashes
        // or hangs, then you'll be left with just the log of the crash or hang.
        // ------------------------------------------------------------------------------------------------
    }
}