Differences
This shows you the differences between the selected revisions of the page.
| debugging 2015-04-24 | debugging 2026-02-03 (current) | ||
| Line 1: | Line 1: | ||
| - | ====== Using Debug Release ====== | + | ====== Using Debug Build ====== |
| - | If I am not able to reproduce a bug you have [[reporting|reported]], I will send you a debug release of WinSCP customized to trace down the bug. | + | If we are not able to reproduce the bug you have [[reporting|reported]], we will send you a debug build of WinSCP customized to trace down the bug. |
| - | Use the debug release as follows: | + | ===== Quick Instructions ===== |
| - | * Uncompress the archive with the executables to an easily accessible location such as folder on your Microsoft Windows desktop or your //My Documents// folder. | + | * The debug build comes in a ZIP archive. |
| - | * Run it. | + | * Save the archive to an easily accessible location such as your Windows desktop or your //My Documents// folder. |
| + | * Extract the archive by opening its context menu (using right-click) and selecting //Extract All// command. | ||
| + | * Locate the extracted ''winscp.exe'' executable and 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. | * 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 ;-) | + | * Close WinSCP. |
| - | * 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 ''[[executables#winscp.com|winscp.com]]'', another trace file is created in ''consoleXXXXtrace.log''. | + | * Windows File Explorer will open with the trace file selected. Open the context menu of the trace file (using right-click) and select //Send to > Compressed (zipped) folder//.· |
| - | * Send me the trace file(s). Please do compress it before sending, if possible. | + | * Email the zipped trace file back to us. |
| - | * Include a regular [[logging|session log]] too, if relevant. | + | * Include a regular [[logging|session log]] too (unless the problem is GUI related only). |
| - | * 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. | + | * Describe the scenario used to reproduce the problem step-by-step for us, including exact times with second precision, exact names of files involved, etc. |
| - | 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//. &wincp | + | ===== [[advanced]] Advanced Instructions ===== |
| - | 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. | + | * If the Windows File Explorer does not open with the trace file, locate it manually in the same folder, where you have extracted the ''winscp.exe'' executable to. The trace file has a name like ''winscpXXXXtrace.log''. |
| + | * If your scenario involves using ''[[executables#winscp.com|winscp.com]]'', another trace file is created as ''consoleXXXXtrace.log''. | ||
| + | * If you do not want to send the trace file(s) via email, we can setup a storage with SFTP access for you easily. Let us know. | ||
| + | * The debug version is slow due to a detailed logging. The slowness may actually prevent the bug from occurring. In such case, let us know, and we will arrange another method for debugging. | ||
| + | * If you do not have a write access to the executables location, the trace file is not created. You might need to run WinSCP with elevated privileges. If you are still not allowed to write to the location, set value of the environment variable ''WINSCPTRACE'' to a directory, where you have a write access to. To set an environment variable, open //Advanced System Properties// (go to //Windows Settings > System > About//, and on Windows 11 follow to //Device Specifications > Related links > Advanced System Settings//, on Windows 10 follow to //Related settings > Advanced System Settings//), click //Environment Variables// and //New// in the //User variables for ...// section. &wincp You can also use ''setx WINSCPTRACE "path"'' command. | ||
| + | * 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. | ||
| + | * In corporate environments, your account profile (including your Windows desktop or your //My Documents// folder) can be located on a network path. It's common that a local policy forbids applications started from a network path from accessing an external network/Internet. If that's the case, and it prevents WinSCP from connecting, please extract the archive to another location on your local drive. | ||