From Kern Sibbald, Bacula author: It is a buffer overrun, which Bacula's smartalloc is detecting and not a free of a non-malloced buffer. Could you please upload your bacula-dir.conf file? I would like to see what directives you are using. Concerning: "Can someone please explain why bacula needs its own memory check stuff which don't gain many but breaks external debuggers like valgrind?" Bacula's smart memory code is superior to anything built into glibc. It detects many problems dynamically with low overhead, and this case clearly shows that it detected a heap corruption apparently caused by a buffer overrun. I have run valgrind many times on Bacula with smartalloc turned on with absolutely no problem so I am not sure what problems you are referring to or why you had to disable it, which is done by a ./configure option.
You may reply to me, or you may post it yourself at http://bugs.bacula.org/view.php?id=1047
