Read access violation at program exit

Anonymous — Mon, 22 Nov 2004 09:27:45 -0000

There is an order of call Category::getInstance and
Appender::ctor so program will be terminated at exit.

More precisely if I call Category::getInstance first (in
order to create own category), further I create new
appender (by new operator) the following internal
functions will be called in specified order:

1. // Due to Category::getInstance
HierarchyMaintainer&
HierarchyMaintainer::getDefaultMaintainer() {
static HierarchyMaintainer _defaultMaintainer;

return _defaultMaintainer;
}

2. // Due to Appender::ctor
Appender::AppenderMap& Appender::_getAllAppenders
() {
static Appender::AppenderMap _allAppenders;

return _allAppenders;
}

Thus destructor for _allAppenders will be called before
dtor for defaultMaintainer.

As I have seen,
HierarchyMaintainer::~HierarchyMaintainer
calls ::_getAllAppenders through shutdown() /
Category::removeAllAppenders, so _getAllAppenders
refers to destroyed _allAppenders.

Recent changes to 79: Read access violation at program exit

Read access violation at program exit