Source: bacula Version: 9.6.3-1 Severity: normal Bacula seems to be configured to unconditionnally send a backtrace when it crashes. The TRACEBACK define seems to be unconditionnally set in `version.h`, regardless of any configuration flag. (Same with DEBUG, by the way.)
Production software should require us to ship with debugging symbols. If it fails and crashes and burn, it should send a proper, actionable, error message instead of going crazy. (My particular situation is a variation of #949366, where bacula-fd would crash after 2 minutes delay because it could bind to the IPv4 port but not IPv6.) -- System Information: Debian Release: 10.3 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
