On 2020-06-22 03:07, Radosław Korzeniewski wrote: > Well, I have a different point of view. In this case SIGABRT is > intentionally raised by the library telling us - I have no idea what is > going wrong and I'm unable to recover from the situation and it is soooo > bad that I have to abort! > It is not a situation where a client executed the library function with > invalid parameters (invalid values, syntax errors or null pointers). In > that case the library should return with error code or SIGSEGV. > > Something goes wrong on the database side or it is a bug in library code.
Radoslaw, for clarification, this comment is concerning the Director crashing when it fails to cancel a hung job, correct? -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
