I recently updated to the new version 0.3.4b. Everything is fine, except the removed shutdown behavoir of the library. In the release notes you write, that you removed the Log4cppCleanup class, since "it was kinda broken anyway". But how is the shutdown supposed to work now.
I found the Category::shutdown method, wich forwards to the HierarchyMaintainer::shutdown. But this removes only all appenders. Nobody is deleting the hierarchy maintainer and with him all the categories (deleteAllCategories).
So how to implement a save shutdown. I would like to use debugging during destruction of static objects. As far as I know, there is no chance to determine the order in wich static objects are destructed. So I can't even call the deleteAllCategories myself and delete the HierarchyMaintainer afterwards.
Any Idea?
Thanks
Dirk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I recently updated to the new version 0.3.4b. Everything is fine, except the removed shutdown behavoir of the library. In the release notes you write, that you removed the Log4cppCleanup class, since "it was kinda broken anyway". But how is the shutdown supposed to work now.
I found the Category::shutdown method, wich forwards to the HierarchyMaintainer::shutdown. But this removes only all appenders. Nobody is deleting the hierarchy maintainer and with him all the categories (deleteAllCategories).
So how to implement a save shutdown. I would like to use debugging during destruction of static objects. As far as I know, there is no chance to determine the order in wich static objects are destructed. So I can't even call the deleteAllCategories myself and delete the HierarchyMaintainer afterwards.
Any Idea?
Thanks
Dirk