Created
November 14, 2018 20:48
-
-
Save kriegsman/5f30dd8315c882703b42c9f5d58f7c0f to your computer and use it in GitHub Desktop.
ClearWayQA ReadMe.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ClearWayQA Plug-In PPC v2.1a5 Read Me | |
6/18/98 | |
"ClearWayQA" is a tool for finding, isolating, and recording two | |
specific kinds of bugs in other WebSTAR plug-ins: memory bugs, and | |
PowerPC processor exceptions. | |
ClearWayQA finds many kinds of memory bugs that other plug-ins may have, | |
such as double-deletes, uninitialized variables, buffer and array | |
overruns, etc. | |
ClearWayQA also traps ALL PowerPC processor exceptions and generates | |
a backtrace file showing where the error occured. If it were not | |
catching these processor exceptions, you would see them as | |
"System Errors" or "Unexpected Quits" from WebSTAR. | |
Using ClearWayQA | |
Install ClearWayQA in your WebSTAR plug-ins folder and restart WebSTAR. | |
If a memory error or a processor error occurs, ClearWayQA will write an | |
entry into the "ClearWayQA.log" file in your WebSTAR root folder. | |
WebSTAR will then quit. You must restart the server computer to re-run | |
WebSTAR, because of WebSTAR's serial-number-checking scheme. | |
You can examine the contents of the ClearWayQA.log file to see | |
what happened, where and when. | |
Remember that even a perfectly written plug-in can be the victim of a | |
memory or processor bug caused by a poorly-written plug-in running | |
on the same server. | |
*** Restarting Your Server *** | |
If you have the program called "Restarter.fire" on your server's hard | |
drive, ClearWayQA can restart your computer after WebSTAR quits. The | |
restart is essentially the same as a Finder-level Restart command. | |
The program "Restarter.fire" is a standard part of the FireSite distribtion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment