1 .\" Hey, EMACS: -*- nroff -*-
2 .\" First parameter, NAME, should be all caps
3 .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
4 .\" other parameters are allowed: see man(7), man(1)
5 .TH BTRACEBACK 1 "6 December 2009" "Kern Sibbald" "Network backup, recovery and verification"
6 .\" Please adjust this date whenever revising the manpage.
9 btraceback \- wrapper script around gdb and bsmtp
17 \fBbtraceback\fR is a simple wrapper shellscript around the \fBgdb\fR debugger
18 (or \fBdbx\fR on Solaris systems) and \fBbsmtp\fR, provided for debugging purposes.
21 \fBbtraceback\fR is called solely by the exception handlers of the Bacula daemons upon
22 an imminent crash. It can also be called interactively to view the
23 current state of the threads belonging to a process.
26 In order to work properly, debugging symbols must be available to the
27 debugger on the system, and gdb, or dbx (on Solaris systems) must be
28 available in the \fB$PATH\fR.
30 If the Director or Storage daemon runs under a non-root uid, it will
31 most likely be needed to modify the \fBbtraceback\fR script to elevate
32 privileges for the call to \fBgdb\fR/\fBdbx\fR, to ensure it has the proper
35 Interactive use of \fBbtraceback\fR is subject to the same risks than live
36 debugging of any program, which means it could cause Bacula to crash under
37 rare and abnormal circumstances. Interactive use is not recommended in
38 production environments.
41 \fBbtracback\fR relies on \fB$PATH\fR to find the debugger.
45 .I /usr/lib/bacula/btraceback
50 .I /usr/sbin/btraceback
52 symbolic link to \fI/usr/lib/bacula/btraceback\fR
55 .I /etc/bacula/scripts/btraceback.gdb
57 the GDB command batch used to output a stack trace
61 This manual page was written by Lucas B. Cohen