Bug#954971: should not try to send a traceback in production

2020-03-27 Thread Antoine Beaupré
On 2020-03-27 09:21:23, Carsten Leonhardt wrote: > Antoine Beaupré writes: > >>> Could you explain how you would want this improved? >> >> I would prefer that no email is sent at all, or have that >> configurable. I would prefer, in fact, that TRACEBACK is disabled at >> compile time, unless the

Bug#954971: should not try to send a traceback in production

2020-03-27 Thread Carsten Leonhardt
Antoine Beaupré writes: >> Could you explain how you would want this improved? > > I would prefer that no email is sent at all, or have that > configurable. I would prefer, in fact, that TRACEBACK is disabled at > compile time, unless the debugging symbols are shipped. At compile time we can't

Bug#954971: should not try to send a traceback in production

2020-03-26 Thread Antoine Beaupré
On 2020-03-26 20:36:15, Carsten Leonhardt wrote: > Hi Antoine, > >> 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

Bug#954971: should not try to send a traceback in production

2020-03-26 Thread Carsten Leonhardt
Hi Antoine, > 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

Bug#954971: should not try to send a traceback in production

2020-03-25 Thread Antoine Beaupre
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