>>>>> On Mon, 22 Jun 2020 09:07:29 +0200, Radosław Korzeniewski said: > > Hello, > > śr., 17 cze 2020 o 19:17 Martin Simmons <mar...@lispworks.com> napisał(a): > > > > That's interesting, because MySQL (actually MariaDB 10.4.12) has not > > > changed since 41 days before I updated Bacula from 9.6.3 to 9.6.5. The > > > problem started only after Bacula updated, which suggests it's not > > > MariaDB's fault. Now that I know how to do per-package build > > > environment overrides on Gentoo, though, it's easy enough to just add > > > the debug flags to dev-db/mariadb. > > > > Yes, this crash is probably not a bug in MariaDB. > > > 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.
Yes, I think you are correct. I possibly meant to say "not a bug in Bacula" but I can't remember now. __Martin _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
