On Wed, Jun 23, 2010 at 1:17 PM, Kern Sibbald <k...@sibbald.com> wrote: > Yes, as Martin says, SIGUSR2 is something that should be ignored. We use it > internally to signal between threads, and when you are running the debugger > on Bacula, you need to tell the debugger to ignore it -- as Martin indicates, > or most often, when I am manually debugging, I start it with "run -s -f ...". > For more information, see the Kaboom chapter of the "Problems" manual. > > Of course, if Bacula sent you the traceback (or put it in your working > directory), you should open a bug report and post it there, and we will look > at it. >
I had to run gdb manually (the e-mail report kept coming back empty) and followed the notes in the manual. I did 'run -s -f ...' as the manual said. I'll ignore SIGUSR2 and get it to crash again. Robert LeBlanc Life Sciences & Undergraduate Education Computer Support Brigham Young University ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users