fcatch — print a stack back-trace of a program as it crashes
fcatch generate stack backtraces from a
running application as it crashes, or upon receiving a variety of
Limit the back-trace to
frames. The default is to limit the back-trace to 10
frames. Specify 0 or "all" to print all
Perform a light-weight stack backtrace containing only minimal information. Equivalent to -print -.
Perform a detailed stack back-trace that includes, where possible, inlined function calls, parameter names and values, and debug-names. Equivalent to -print inline,params,debug-names.
Specify the level of detail to include in a stack
print-option can be
debug-names: use debug information, such as DWARF, to determine the name of functions
paths: include the full path to source files and libraries
inline: include in-line function in back-trace
locals: to include local variables from each frame
params: include the function parameters
To negate a
it with "-".
The full path of the executable to read.
Do not attempt to read the corresponding executable when loading a core file.
The system root directory under which all executables, libraries, and source are located.
Set internal debug-tracing of the specified
level (level can be NONE,
INFO, WARNING, FINE, and FINEST). If
level is absent, FINE is
assumed; if the
class is absent,
the global level is set.
Report bugs to http://sourceware.org/frysk