[krbdev.mit.edu #2862] Memory leak in krb5-libs up to 1.3.6

[Bojan Smojver via RT]

Quoting Tom Yu via RT <rt-comment at krbdev.mit.edu>:

> I have looked at the code in postgresql-7.4.5 (I don't have 7.4.6
> handy), as well as at the krb5 ccache code, and it seems that the
> failure you're seeing is "impossible".  Since you appear to be running
> a multi-threaded application, I strongly suggest that you try out the
> krb5-1.4 beta release.  Releases prior to krb5-1.4 are known to have
> thread-safety issues, which may be part of your problem.

Aha! I'm running this inside Apache 2.0.52. I have two different version of
Apache - one that runs a worker model (multi threaded) and one that runs
prefork (not multi threaded). I'll compare and let you know.

> Does the new glibc give stack traces on double-free and other
> memory-management error conditions if debugging symbols are available?
> Or do you need to use something like valgrind?

Normally I just load postgresql-debuginfo and krb5-debuginfo RPMS, which contain
debugging symbols, and then run the binary (Apache) inside gdb. Once the thing
crashes, I do a backtrace. I'm not an expert in this, so maybe there are better
ways...


--
Bojan