>>>>> On Mon, 13 Jul 2020 10:12:41 -0400, Phil Stracchino said: > > On 2020-07-13 10:04, Radosław Korzeniewski wrote: > > Hello, > > > > niedz., 12 lip 2020 o 21:14 Phil Stracchino <ph...@caerllewys.net > > <mailto:ph...@caerllewys.net>> napisał(a): > > > > There appear to be two failures occurring, the SIGUSR2 at > > LZ4_decompress_generic+0x03a2 in the SD, > > > > > > AFAIK, the SIGUSR2 is used internally by Bacula with a watchdog/timeout > > code and it is not a failure in any case especially when you try to > > debug it under debugger. > > > > Ah, so this is a *symptom* of the other problem? Thanks Radosław.
It could be a symptom or it could be unrelated (and it might have happened anyway). After you attach, you could use the dbx command: ignore USR2 to prevent it from stopping on SIGUSR2. In general, if you get the dbx prompt unexpectedly, use the dbx commands: where threads to get some context. __Martin _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
