In order to work properly, debugging symbols must be available to the
debugger on the system, and gdb, or dbx (on Solaris systems) must be
available in the $PATH.
If the Director or Storage daemon runs under a non-root uid, you will
probably need to be modify the btraceback script to elevate
privileges for the call to gdb/dbx, to ensure it has the proper
permissions to debug when called by the daemon.
Although Bareoss use of btraceback within its exception handlers is
always safe, manual or interactive use of btraceback is subject to the
same risks than live debugging of any program, which means it could cause
Bareos to crash under rare and abnormal circumstances. Consequently we
do not recommend manual use of btraceback in production environments
unless it is required for debugging a problem.