ZeroBUGS -- Documentation

Environment Variables

LD_LIBRARY_PATH
This is a system variable, a colon-delimited list of paths; it needs to include the path to the ZeroSystems runtime (libzrt.so).

ZERO_AUTO_RTTI
Type: boolean Default: true
By default, the debugger attempts to determine the dynamic type of objects referred to by pointers or references. For example, when debugging a function that takes a pointer-to-base argument, the debugger may display it as a pointer-to-derived. Use this environment variable if you want to turn off this feature.

ZERO_CACHE_SYMBOLS
Type:boolean Default: false
When true, the debugger will cache symbol table information under the config path directory, so that the next time a program is debugged the information is readily available, cross-indexed, and the reading ELF symbol table sections can be skipped.

ZERO_CONFIG_PATH
Type: string Default: current installation directory.
Points to a directory where a directory named .zero is automatically created (and updated, after each execution of the debugger). The .zero/config file stores state and history information that include, for example, the breakpoints that are currently set in the debugged program, so that they can be restored automatically in a future debugging session. If the variable is not set, the current installation directory is assumed.

ZERO_CUSTOM_THEME
Type: boolean Default: true
Enable the custom look of certain controls, such as notebook tabs.

ZERO_D_SUPPORT
Type: boolean Default: false
When true, support for the The D Programming Language is enabled.

ZERO_DEBUG_SYMBOLS_DIR
Type: string Default: /usr/lib/debug
Points to a directory where external debug symbols files reside.

ZERO_ENABLE_GCC_WORKAROUNDS
Type: boolean Default: false
Enable miscellaneous workarounds -- for example: gcc 2.95 generates incorrect source line information in DWARF (symptom: instead of the source code listing you see assembly instructions).

ZERO_EXPENSIVE_TYPE_LOOKUPS
Type: unsigned int Default: 1
If set, attempt to find the full type definition, rather than just being happy with a forward declaration that matches. Values:

1: look for type definition inside functions;

2: if a full definition is not found in the current module, lookup all program modules.

You may turn it off (set to 0) for better performance when debugging large programs.

ZERO_HARDWARE_BREAKPOINTS
Type: boolean Default: true
Turn on/off use of hardware support for breakpoints. Useful when debugging the engine and when running on some broken hardware emulators.

ZERO_HIGHLIGHT_CHANGES
Type: string Default: magenta
The color to use for showing changes in variables, registers, and raw memory.

ZERO_HELP_PATH
Type: string Default: install-path/help.
Points to the directory that contains the online help files.

ZERO_LINE_NEAREST_MATCH
Type: bool Default: true.
Zero uses some heuristics to determine the nearest match when looking up the source line that corresponds to an arbitrary code address. To disable this behavior and get results that are closer to what GDB would produce (albeit not necessarily correct), you may set this variable to 0, or "false".

ZERO_MAX_ARRAY
Type: integer Default: 100
Maximum array elements to be shown. Once the maximum number is reached a "..." element is displayed, followed by the last two array elements.

ZERO_MAX_MACRO
Type: integer Default: 5000
Maximum macroprocessor definitions, per compilation unit, looked up by the built-in expression interpreter. When evaluating an expression like min(a,b) the interpreter looks up the first N macros in the current compilation unit, trying to find a match for "min". If no match is found, the symbol tables are then searched. Set it to 0 for unlimited macros.

ZERO_MAX_STACK
Type: integer Default: 1024
Maximum size of stack traces. It is useful to limit the the size of the stack traces when dealing with infinite recursion bugs.

ZERO_PATH_MAP
Type: string Default: empty
A list of semicolon-separated string pairs; the delimiter between the first element and the second is a colon.

ZERO_PROCFS
Type: string Default: /proc/
Tell the debugger what is the root of the procfs filesystem. Useful on systems that mount the proc filesystem in a non-standard location (see the mount_linprocfs on FreeBSD).

ZERO_PLUGIN_PATH
Type: string Default: install-path/plugin.
Tells the engine where to look for plugins; it is a colon delimited list of paths.

ZERO_RIGHT_CLICK_SCOPE
Type: string Default: unit
Legal values are all, module, unit. Sets the scope for looking up symbols under the cur"sor when the third mouse button is clicked.

ZERO_START_MAIN
Type: boolean Default: false
Start debugging at main(). Equivalent to using the --main command line option.

ZERO_STABS_LAZY
Type: boolean Default: true
Applies to the default STABS reader plugin. If set, stabs are read lazily. The command line option --stabs-now overrides this environment variable.

ZERO_SOURCE_STEP
Type: boolean Default: true
Step over when coming from region of code that has source code, into a portion where there's no available source code (thus avoiding tracing thru library and compiler-generated code, such as operator new, for example).

ZERO_USE_FRAME_HANDLERS
Type: boolean Default: false
When set, instructs the debugger to use the stack unwinding information generated by the compiler, when available, rather than using the frame pointer register. This feature enables debugging programs compiled with -fomit-frame-pointer.
Note: The STABS debug format does not provide frame unwinding information. Older versions of GCC such as 2.95 did not use the DWARF format by default. If you have an older GCC, compile your programs with -gdwarf-2, or -gdwarf-2n, where n is the debug level, 3 being the most verbose.

	Environment Variables `LD_LIBRARY_PATH` This is a system variable, a colon-delimited list of paths; it needs to include the path to the ZeroSystems runtime (libzrt.so). `ZERO_AUTO_RTTI` Type: boolean Default: true By default, the debugger attempts to determine the dynamic type of objects referred to by pointers or references. For example, when debugging a function that takes a pointer-to-base argument, the debugger may display it as a pointer-to-derived. Use this environment variable if you want to turn off this feature. `ZERO_CACHE_SYMBOLS` Type:boolean Default: false When true, the debugger will cache symbol table information under the config path directory, so that the next time a program is debugged the information is readily available, cross-indexed, and the reading ELF symbol table sections can be skipped. `ZERO_CONFIG_PATH` Type: string Default: current installation directory. Points to a directory where a directory named .zero is automatically created (and updated, after each execution of the debugger). The .zero/config file stores state and history information that include, for example, the breakpoints that are currently set in the debugged program, so that they can be restored automatically in a future debugging session. If the variable is not set, the current installation directory is assumed. `ZERO_CUSTOM_THEME` Type: boolean Default: true Enable the custom look of certain controls, such as notebook tabs. `ZERO_D_SUPPORT` Type: boolean Default: false When true, support for the The D Programming Language is enabled. `ZERO_DEBUG_SYMBOLS_DIR` Type: string Default: `/usr/lib/debug` Points to a directory where external debug symbols files reside. `ZERO_ENABLE_GCC_WORKAROUNDS` Type: boolean Default: false Enable miscellaneous workarounds -- for example: gcc 2.95 generates incorrect source line information in DWARF (symptom: instead of the source code listing you see assembly instructions). `ZERO_EXPENSIVE_TYPE_LOOKUPS` Type: unsigned int Default: 1 If set, attempt to find the full type definition, rather than just being happy with a forward declaration that matches. Values: 1: look for type definition inside functions; 2: if a full definition is not found in the current module, lookup all program modules. You may turn it off (set to 0) for better performance when debugging large programs. `ZERO_HARDWARE_BREAKPOINTS` Type: boolean Default: true Turn on/off use of hardware support for breakpoints. Useful when debugging the engine and when running on some broken hardware emulators. `ZERO_HIGHLIGHT_CHANGES` Type: string Default: magenta The color to use for showing changes in variables, registers, and raw memory. `ZERO_HELP_PATH` Type: string Default: install-path/help. Points to the directory that contains the online help files. `ZERO_LINE_NEAREST_MATCH` Type: bool Default: true. Zero uses some heuristics to determine the nearest match when looking up the source line that corresponds to an arbitrary code address. To disable this behavior and get results that are closer to what GDB would produce (albeit not necessarily correct), you may set this variable to 0, or "false". `ZERO_MAX_ARRAY` Type: integer Default: 100 Maximum array elements to be shown. Once the maximum number is reached a "..." element is displayed, followed by the last two array elements. `ZERO_MAX_MACRO` Type: integer Default: 5000 Maximum macroprocessor definitions, per compilation unit, looked up by the built-in expression interpreter. When evaluating an expression like min(a,b) the interpreter looks up the first N macros in the current compilation unit, trying to find a match for "min". If no match is found, the symbol tables are then searched. Set it to 0 for unlimited macros. `ZERO_MAX_STACK` Type: integer Default: 1024 Maximum size of stack traces. It is useful to limit the the size of the stack traces when dealing with infinite recursion bugs. `ZERO_PATH_MAP` Type: string Default: empty A list of semicolon-separated string pairs; the delimiter between the first element and the second is a colon. `ZERO_PROCFS` Type: string Default: /proc/ Tell the debugger what is the root of the procfs filesystem. Useful on systems that mount the proc filesystem in a non-standard location (see the mount_linprocfs on FreeBSD). `ZERO_PLUGIN_PATH` Type: string Default: install-path/plugin. Tells the engine where to look for plugins; it is a colon delimited list of paths. `ZERO_RIGHT_CLICK_SCOPE` Type: string Default: unit Legal values are **all, module, unit. Sets the scope for looking up symbols under the cur"sor when the third mouse button is clicked. `ZERO_START_MAIN` Type: boolean Default: false Start debugging at main(). Equivalent to using the --main command line option. `ZERO_STABS_LAZY` Type: boolean Default:** true Applies to the default STABS reader plugin. If set, stabs are read lazily. The command line option --stabs-now overrides this environment variable. `ZERO_SOURCE_STEP` Type: boolean Default: true Step over when coming from region of code that has source code, into a portion where there's no available source code (thus avoiding tracing thru library and compiler-generated code, such as operator new, for example). `ZERO_USE_FRAME_HANDLERS` Type: boolean Default: false When set, instructs the debugger to use the stack unwinding information generated by the compiler, when available, rather than using the frame pointer register. This feature enables debugging programs compiled with -fomit-frame-pointer. Note: The STABS debug format does not provide frame unwinding information. Older versions of GCC such as 2.95 did not use the DWARF format by default. If you have an older GCC, compile your programs with -gdwarf-2, or -gdwarf-2n, where n is the debug level, 3 being the most verbose.

Home \| Top \| Up \| Previous \| Next \| Community