I've wrote a example app below that illustrates the problem.
Any suggestions?
Kevin ( listman)
This is the exception
Unhandled exception at 0x77f5d61b in testing.exe: 0xC005: Access
violation writing location 0x100ad678.
This is the stack
ntdll.dll!77f5d61b()
ntdll.dll!77f42044()
nd,
bool bufferedIO, int bufferSize)
{
synchronized sync(this);
I'm going to try to go to CVS Head
Curt Arnold wrote:
On Jan 6, 2005, at 12:32 PM, Kevin Tew wrote:
I've wrote a example app below that illustrates the problem.
Any suggestions?
Kevin ( listman)
The threading code in the cur
Curt Arnold wrote:
On Jan 6, 2005, at 4:45 AM, Ceki Gülcü wrote:
Curt,
While you are importing unit tests over from log4j, you probably
became aware that the log4j tests based on the witness approach,
although very valuable, are fragile and somewhat hard to maintain. I
suspect that better and cheap
Curt,
Sorry about that empty post, I was trying to get the list address.
WIN32:
I've used ant and done a lot of building open source projects from
source, but I could use some pointers with cpptasks.
1. I have ant and cpptasks.
2. I've put cpptask in the ant/lib folder.
D:\buildlogging\logging-log
This is what it took for me to build
Kevin
--- logging-log4cxx-orig/configure.in 2004-12-26 00:31:52.0 -0700
+++ logging-log4cxx/configure.in2005-01-07 10:13:30.0 -0700
@@ -381,6 +381,7 @@
include/log4cxx/xml/Makefile
include/log4cxx/config/Makefile
include/log4cxx/db/Make
I want to use log4cxx with an app that is already using apr-0.
The windows version of my app seems to work just fine.
The linux version of my app segfaults as
#0 0x40e7c1ea in apr_atomic_add32 (mem=0x8051944, val=1) at
atomic/unix/apr_atomic.c:213
#1 0x40e7c378 in apr_atomic_inc32 (mem=0x0) at
Platform Debian sid up to date
Note I'm building using autoconf/automake and I'm supplying
/usr/local/apr the configure script as the apr location
ldd liblog4cxx.so.9.0.0
libapr-1.so.0 => /usr/local/apr/lib/libapr-1.so.0 (0x40101000)
librt.so.1 => /lib/tls/librt.so.1 (0x40138000)
eleton' : inherits
'log4cxx::Appender::log4cxx::Appender::getClass' via dominance
c:\Branches\main\cb\ExternalLibs\include\log4cxx\appender.h(56)
: see declaration of 'log4cxx::Appender::getClass'
I was also wondering about the state of the rollingfileappender?
Does log4cxx provided wrapped string conversion routines from const
char* variables to log4cxx::LogString?
My log4cxx::LogString is defined as a std::basic_string
Thanks
Kevin Tew
Curt Arnold wrote:
On May 10, 2005, at 1:06 PM, Kevin Tew wrote:
I'm getting tons of these warnings for every log4cxx class
Any Ideas?
c:\Branches\main\cb\ExternalLibs\include\log4cxx\helpers
\appenderattachableimpl.h(106) : warning C4250:
'log4cxx::helpers::AppenderAttachableImpl&#
