Using Debug Build

If I am not able to reproduce a bug you have reported, I will send you a debug build of WinSCP customized to trace down the bug.

Use the debug release as follows:

• Uncompress the archive with the executables to an easily accessible location such as folder on your Windows desktop or your My Documents folder.
• Run it.
• Reproduce the problem you are having. Please use the most simple scenario for that. Avoid doing any operation with WinSCP that is not strictly necessary to make the problem reproduce.
• Close WinSCP, if it have not crashed already because of the bug
• A trace file should have been created in the same folder, where you have stored the executables to, under name like winscpXXXXtrace.log. If your scenario involves using winscp.com, another trace file is created in consoleXXXXtrace.log.
• Send me the trace file(s). Please do compress it before sending, if possible.
• Include a regular session log too, if relevant.
• If you do not want to send the trace file(s) via email, I can setup a storage with SFTP access for you easily. Let me know.

You may not have a write access to the executables location. On Windows Vista &winvista and newer, you might need to run WinSCP with elevated privileges. If you are still not allowed to write to the location, set value of environment variable WINSCPTRACE to directory, where you have a write access to. To set an environment variable go to Control Panel > System and Security > System > Advanced System Settings > Advanced > Environment Variables > User variables for … > New.

The trace file may contain a sensitive information. We do respect your privacy. We will never misuse any information we find in the trace file, nor we will ever share the information with a third party. You can remove anything you do not want to share.