C++ logging library. It is extremely powerful, extendable, light-weight, fast performing, thread and type safe and consists of many built-in features. It provides ability to write logs in your own customized format. It also provide support for logging your classes, third-party libraries, STL and third-party containers etc.
I am using the library within a DLL. When the dll loads, I didnt not configure the log file name. (NOTE : ELPP_NO_DEFAULT_LOG_FILE is used) There will be a message of "Could not load empty file for logging, please re-check your configurations for level".
However, this is not the real problem. Afterwards, when the DLL functions are used I set the Log File Name to my desired one. It works fine until the first LOG macro is called. Inside the log file, the dispatch function within the library repeatedly prints the message (The timestamps for the logs are the same) This then results in me having an extremely large log file making my system crash afterwards.
Are there any clues where I can look for to solve this?
I am using the library within a DLL. When the dll loads, I didnt not configure the log file name. (NOTE : ELPP_NO_DEFAULT_LOG_FILE is used) There will be a message of "Could not load empty file for logging, please re-check your configurations for level".
However, this is not the real problem. Afterwards, when the DLL functions are used I set the Log File Name to my desired one. It works fine until the first LOG macro is called. Inside the log file, the dispatch function within the library repeatedly prints the message (The timestamps for the logs are the same) This then results in me having an extremely large log file making my system crash afterwards.
Are there any clues where I can look for to solve this?