We are using Log4CPP in our VC++ 2013 project and it is crashing the
application. Any help is much appreciated.
Usual source of such kind of issues is DLL/EXE runtime mismatch. You
need to check how you build your EXE (what runtime used) and how you
build log4cpp DLL (same; what runtime used?).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
We are using Log4CPP in our VC++ 2013 project and it is crashing the application. Any help is much appreciated.
Following are the details:
Log4cpp version : 1.1.3 downloaded from https://sourceforge.net/projects/log4cpp/files/
64-bit application running in Windows 7.
Following is the dump analysis
Function
ntdll!NtWaitForMultipleObjects+a
KERNELBASE!WaitForMultipleObjectsEx+e8
kernel32!WaitForMultipleObjectsExImplementation+b3
kernel32!WerpReportFaultInternal+215
kernel32!WerpReportFault+77
kernel32!BasepReportFault+1f
kernel32!UnhandledExceptionFilter+1fc
ntdll! ?? ::FNODOBFM::`string'+2025
ntdll!_C_specific_handler+8c
ntdll!RtlpExecuteHandlerForException+d
ntdll!RtlDispatchException+45a
ntdll!KiUserExceptionDispatch+2e
ntdll!RtlFreeHeap+1a5
kernel32!HeapFree+a
msvcr120!free+1c
A!log4cpp::PatternLayout::format+129
A!log4cpp::FileAppender::_append+36
A!log4cpp::AppenderSkeleton::doAppend+3f
A!log4cpp::Category::callAppenders+4d
A!log4cpp::Category::_logUnconditionally2+64
A!log4cpp::Category::_logUnconditionally+40
A!log4cpp::Category::info+41
A!main+56c
A!__tmainCRTStartup+10f
kernel32!BaseThreadInitThunk+d
ntdll!RtlUserThreadStart+1d
THanks !
On 09/05/2017 07:43 AM, Neel Hayatnagarkar wrote:
Usual source of such kind of issues is DLL/EXE runtime mismatch. You
need to check how you build your EXE (what runtime used) and how you
build log4cpp DLL (same; what runtime used?).