Ceph

I re-ran this on the latest code, and I saw a bunch of "potential leaks" related to allocating std::strings in the ConfFile. But these are all bogus because when the ConfFile is destroyed, those strings will all be freed.

I think valgrind is complaining about this because g_conf, a global, is creating a ConfFile. That ConfFile, and the memory inside it, won't be freed until g_conf is destroyed. But since g_conf has the special init_priority(103) attached to it, that happens after every other global has been destroyed. Perhaps valgrind's own analysis is running before that destructor is getting called?

Anyway, these are certainly not real memory leaks. If anyone has any idea how to get rid of these annoying warnings, it would be welcome. However, until then, this bug will have to be closed, or dormant, or something.

I don't see any obvious way to get valgrind to stop warning about these "potential leaks" which are not leaks at all. I think this is just something we're going to have to filter out. It only shows up when you run with --leak-check=full