Comment 5 for bug 246298

If Fortify source is turned of the problem *is* fixed and not simply hidden.

The output indicates that that this crash is due to the fact that Bacula was built with -DFORTIFY_SOURCE=2 (please check spelling). The glibc code that implements this feature according to the authors of the code may generate false positives, and that is indeed the case here. The code reports a buffer overflow where one does *not* exist.

This problem is easily detected because after building Bacula and running any test case, it crashes the first and every time.

Solution:
1. Build Bacula without the fortify source option. It is unnecessary, a flawed implementation, and Bacula does its own checking for these things.

2. Please always run the regression scripts after building a new version.

Best regards,

Kern