[ 
https://issues.apache.org/jira/browse/LOGCXX-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thorsten Schöning resolved LOGCXX-389.
--------------------------------------
    Resolution: Cannot Reproduce

Because we are trying to reduce the backlog of open issues, I'm closing this 
one right now. The described environment in which the problem has been reported 
originally is pretty outdated these days and things might have been fixed 
already with a newer version of log4cxx and/or a new environment. If this 
concrete problem is still relevant for someone, feel free to reopen and provide 
the necessary details. Otherwise it's best to create a new issue describing the 
new environment and problem.

> Crash on Windows 2008 (x64)
> ---------------------------
>
>                 Key: LOGCXX-389
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-389
>             Project: Log4cxx
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.10.0
>         Environment: Windows 2008 R2 SP1 (x64), Visual Studio 2008
>            Reporter: Shane Galvin
>            Assignee: Curt Arnold
>            Priority: Critical
>
> Seeing a crash on Windows 2008 R2 SP1 (x64) with the following stack trace, 
> while attempt to log an info message, application is multithreaded. Also am 
> wondering if log4cxx 0.10.0 is compatible with APR 1.4.5?
> ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute 
> [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]
> LAST_CONTROL_TRANSFER:  from 0000000076dc301a to 00000000770132d0
> FAULTING_THREAD:  ffffffffffffffff
> BUGCHECK_STR:  
> APPLICATION_FAULT_STACK_OVERFLOW_STRING_DEREFERENCE_FILL_PATTERN_ffffffff
> PRIMARY_PROBLEM_CLASS:  STACK_OVERFLOW_FILL_PATTERN_ffffffff
> DEFAULT_BUCKET_ID:  STACK_OVERFLOW_FILL_PATTERN_ffffffff
> STACK_TEXT:  
> 00000000`6294e800 00000000`770132d0 ntdll!RtlFreeHeap+0xd0
> 00000000`6294e880 00000000`76dc301a kernel32!HeapFree+0xa
> 00000000`6294e8b0 00000000`71fccabc msvcr90!free+0x1c
> 00000000`6294e8e0 00000000`68799f71 msvcp90!std::basic_string<unsigned 
> short,std::char_traits<unsigned short>,std::allocator<unsigned short> 
> >::~basic_string<unsigned short,std::char_traits<unsigned 
> short>,std::allocator<unsigned short> >+0x19
> 00000000`6294e910 00000000`629e34f5 
> log4cxx!log4cxx::WriterAppender::subAppend+0xa5
> 00000000`6294e990 00000000`629e2a91 
> log4cxx!log4cxx::WriterAppender::append+0x31
> 00000000`6294e9c0 00000000`6296023a 
> log4cxx!log4cxx::AppenderSkeleton::doAppend+0x27a
> 00000000`6294eab0 00000000`62957ffa 
> log4cxx!log4cxx::helpers::AppenderAttachableImpl::appendLoopOnAppenders+0x8a
> 00000000`6294eaf0 00000000`629ad5e3 
> log4cxx!log4cxx::Logger::callAppenders+0xa3
> 00000000`6294eb60 00000000`629ad93b log4cxx!log4cxx::Logger::forcedLog+0xdb
> 00000000`6294ec10 00000000`629ae22c log4cxx!log4cxx::Logger::info+0x3c



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to