>>>>> On Wed, 11 Sep 2019 22:22:07 -0700, Chandler said: > > Martin Simmons wrote on 9/9/19 03:33: > > A useful trick for finding similar reports is to search the internet for the > > functions listed near the top of the backtrace. In this case, googling for: > > > > bacula "clear_slot" "set_slot" > > > > leads to this bug report: > > > > https://bugs.bacula.org/view.php?id=2231 > > > > where kern suggests compiling with -O0 as a workaround. > > > > Thanks, using -O0 does work, but how did you pick out clear_slot and set_slot > from that mess?
I looked for "signal" in the thread backtraces to find which one got signal 11. These functions were at the top of the stack when the signal handler was called: > Thread 3 (Thread 0x7ffff6d47700 (LWP 9925)): > #0 0x00007ffff7d2e0ca in __waitpid (pid=pid@entry=9927, > stat_loc=stat_loc@entry=0x7ffff6d45bcc, options=options@entry=0) at > ../sysdeps/unix/sysv/linux/waitpid.c:30 > #1 0x00007ffff7f8b953 in signal_handler (sig=11) at signal.c:237 > #2 <signal handler called> > #3 VOLRES::set_slot (slot=-1, this=0x5555555555555555) at vol_mgr.h:88 > #4 DEVICE::clear_slot (this=0x7fffe80018e8) at dev.c:1444 __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
