[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bacula-devel] "buffer overflow detected" error on fedora distributions.
On Monday 11 February 2008 17.20:40 Josh Fisher wrote:
> Scott Barninger wrote:
> > Josh,
> >>>> Please note that the patch also removes the cp of static-bacula-fd for
> >>>> fc8. This is because the static bacula-fd will not compile on Fedora 8
> >>>> with glibc 2.7-2, apparently due to a glibc bug. At least, I couldn't
> >>>> get it to compile.
> > Please see my note a few moments ago to the devel and users lists with a
> > new release to fix this issue with FORTIFY_SOURCE. I have no idea why
> > you had a problem with static compile. I've had no such issue building
> > on fc8 at all. Thanks for your input.
> I believe it's only on x86_64, possibly only AMD64, and is due to the
> vDSO version of clock_gettime() being called in pthread_cond_timedwait()
> for static builds. The vDSO version is not available for static linking.
> See http://sources.redhat.com/bugzilla/show_bug.cgi?id=5465. It is
> fixed, but hasn't made it to an FC8 update yet.
If I am not mistaken, the most common reason for static linking Bacula is for
use on the rescue disk, and I have been wanting for some time to eliminate
the need for a static FD on that disk. The shared library version may
already work, but with just one or two additional lines of code, we could
guarantee that it will work, which would remove the need for a statically
If anyone is interested in this little project, I would be happy to point them
to the shell scripts that need to be updated ...
One of the big problems with static linking (aside from the above type of
bugs) is that as far as I know the OpenSSL code does not have static
libraries, which means that it is not possible to build a statically linked
FD with encryption turned on.
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Bacula-devel mailing list
This mailing list archive is a service of Copilotco.