Access Violation (ntdll.dll) when default destructor called at program termination

[fkahhaleh]

Hi,

I just started using this library and it seems there is a lot of potential to it.
Right off the bat, when using it with the simple "Getting started" example in the Readme.

Env:
Win 7 (64bit).
VS 2013 Community Edition.
Win32 C++ project.
Using EasyLogging++ v8.91 (C++<11)

Details:
I hit a snag. I get a "example1.exe has triggered a breakpoint" error.
BreakPoint is then shown at LN:586 (easylogging++.h file).

STDOUT + FILE both show the log message so it is going through with it.

OUTPUT tab in VS shows:
Critical error detected c0000420
example1.exe has triggered a breakpoint.

CallStack tab in VS shows:
http://pastebin.com/TyVWRvtd

EDIT-1
So I did more tracing, and it seems this happens after my main program finishes.
In my test, I only have a small main function that just logs a single line and returns 1.
All is good until I return, which signals end of program execution. there the destructor of Mutex class gets called multiple times afterwards, and hits that Access Violation error on ntdll.dll.

EDIT-2
I can use C++11, so I tried the latest v9.8 and it didn't suffer from this issue. So I am not sure
if this is a real bug or it is compatibility with previous c++ compilers, not that I have done anything
specific with defining (or lack there of).

End EDIT

Any hints or suggestions on how to move forward is appreciated.

Thanks

[easylogging]

oh if you are referring to version 8 then it's not maintained anymore. Please consider using 9.8 or higher version