This shows you the differences between two versions of the page.
|
dev:debugging:home [2009/12/04 03:50] tdo |
dev:debugging:home [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Environment Variable: omnidex_debug ====== | ||
| - | ===== Omnidex Debugging ===== | ||
| - | Omnidex supports a sophisticated debugging system that can aid in checking for application issues. | ||
| - | |||
| - | The following variables can be set to enable debugging, prior to starting an application. For client/server applications, set these variables prior to starting the Omnidex Network Services listener to enable debugging on that listener. The required variables (above) must also be set. | ||
| - | |||
| - | |||
| - | ==== OMNIDEX_DEBUG ==== | ||
| - | |||
| - | OMNIDEX_DEBUG enables debugging. The settings must be quoted and multuple settings must be comma separated. Debugging information is output to odxdebug.log by default. Use the FILE=filename setting or the OMNIDEX_DEBUG_FILE environment variable to override this default. | ||
| - | |||
| - | Following is a list of valid settings: | ||
| - | |||
| - | **ON | OFF** - Off by default. Enables general debugging for oa routines. | ||
| - | |||
| - | **DATABASE** - Provides additional debugging information pertaining to the database interaction. | ||
| - | |||
| - | **FILESYSTEM** - Provides additional debugging information pertaining to issues with files or the filesystem. | ||
| - | |||
| - | **OPTIMIZER** - Provides additional debugging information pertaining to the optimizer. | ||
| - | |||
| - | **QUALIFY** - Provides additional debugging information pertaining to oaqualify and the QUALIFY command. | ||
| - | |||
| - | **SELECT** - Provides additional debugging information pertaining to oaselect and the SELECT command. | ||
| - | |||
| - | **UPDATE** - Provides additional debugging information pertaining to oaupdate and the UPDATE command. | ||
| - | |||
| - | **CONNECT** - Provides additional debugging information pertaining to oaconnect and the CONNECT command. | ||
| - | |||
| - | **KERNEL** - Provides additional debugging information pertaining problems with the Omnidex Kernel. | ||
| - | |||
| - | **FILE=filename** - Writes the debug output to the specified filename. Default output goes to odxdebug.log. Can also override the output destination with the OMNIDEX_DEBUG_FILE environment variable. | ||
| - | |||
| - | **EXCEPTIONS** - Locate an error in a long complex sequence of steps. Outputs the exception and the sequence of steps leading up to the exception. | ||
| - | |||
| - | **ALL** - Output ALL debug information for ALL of the above profiles. CAUTION: The output will be very large. Use this option ONLY if you really need it! | ||
| - | |||
| - | Unix | ||
| - | export OMNIDEX_DEBUG="ON" | ||
| - | |||
| - | Windows | ||
| - | set OMNIDEX_DEBUG="DATABASE,FILE=c:\omnidex\log\debug.txt" | ||
| - | |||
| - | |||
| - | |||
| - | ==== OMNIDEX_DEBUG_FILE ==== | ||
| - | |||
| - | OMNIDEX_DEBUG_FILE outputs debugging details to the specified file. Used in conjunction with OMNIDEX_DEBUG. If not set, debug messages will be output to odxdebug.log on the server. The output file can also be set using the FILE=filename option of OMNIDEX_DEBUG. | ||
| - | |||
| - | Unix | ||
| - | export OMNIDEX_DEBUG="SELECT" | ||
| - | export OMNIDEX_DEBUG_FILE="debug.file" | ||
| - | |||
| - | Windows | ||
| - | set OMNIDEX_DEBUG="DATABASE,FILESYSTEM" | ||
| - | set OMNIDEX_DEBUG_FILE="debug.file" | ||
| - | |||
| - | |||
| - | ====== Quick Links ====== | ||
| - | {{page>:quicklinks&nofooter&noeditbtn}} | ||