I2023: Debugging FreeProxy using the debug version of the program
Versions: FreeProxyClient V3.5 onwards
Date reported: 02 November 2003
You have been asked by support to run the debug version of the program. This program is exactly the same as the non-debug from a function point of view except it displays additional information which will better enable a fault diagnosis to be made.
Download the debug version of the FreeProxy server
Substitute the program for the non-debug existing program
Unzip freeproxyd.zip. It contains the server program "freeproxy.exe". In the meantime, place this program in C:Temp for example.
Rename the existing program in C:Program FilesHand-Crafted SoftwareFreeProxy from freeproxy.exe to say freeproxy.exe.sav
Copy C:Tempfreeproxy.exe to C:Program FilesHand-Crafted SoftwareFreeProxyfreeproxy.zip
Change the settings in FreeProxy
In the FreeProxy Control Centre, select Options è Debug Level
Use the drop-down to select "Full trace"
Set output to "Log file and screen"
Set Log access data
Fill in a log file name
Fill in a file name for the access log file
Check Allowed, Forbidden and Default
In each Port setting, make sure you have checked "Report all connects ?", and Done
File -> Save
Prepare the test
Stop the FreeProxy service and any console mode program. You should see:
Service: Not Installed
Console: Not running
displayed in the Stop/Start option of the FreeProxy Control Centre
Delete (or move) any existing log files so that the test starts from the beginning of the log file
Start FreeProxy ONLY in Console mode. There must be only one version of FreeProxy running. Do not start the service.
Start the test
Access the web in the normal way. During the test, the access is likely to be a lot slower than normal because of the amount of data being displayed on the screen. Once you have encountered the problem:
Stop the FreeProxy console
Set the Options -> Debug level to No debug and the other indicators to their pre-test values
Resume operation. There is no need to replace the FreeProxy.exe program back to its saved version as the performance degradation is very slight. You can do this once the program has been rectified by support