Nabble - Log4cxx - Users

Using log4cxx::logstream in generic programming

2009-12-18T14:08:10Z

Hi all,

I'd like to be able to use log4cxx::logstream instances within generic
programming. My goal is pass log4cxx::logstream instances into
templated code expecting basic_ostream instances and have everything
work out.

I've run into two problems.

First, there's no generic way to use std::endl for both
log4cxx::logstream and std::basic_ostream. Here's a test case against
log4cxx 0.10.0 that illustrates the difficulty:

#include <iostream>
#include <log4cxx/logger.h>
#include <log4cxx/stream.h>

template< typename OStream >
void test_it(OStream & os)
{
// std::endl<Elem,Tr> can be deduced for std::cout argument
// std::endl<Elem,Tr> cannot be deduced for log4cxx::logstream argument
os << "Foo" << std::endl;

// std::endl<char,std::traits<char> > works for std::cout and
// log4cxx::logstream
os << "Bar" << std::endl<char, std::char_traits<char> >;

// std::endl<typename OStream::char_type, std::char_traits<typename
// OStream::char_type> works for std::cout but does not work for
// log4cxx::logstream due to no char_type typedef
os << "Baz" << std::endl<typename OStream::char_type,
std::char_traits<typename OStream::char_type> >;
}

int main(int argc, char* argv[]) {

test_it(std::cout);

log4cxx::LoggerPtr logger = log4cxx::Logger::getRootLogger();
log4cxx::logstream logstream(logger, log4cxx::Level::getInfo());

test_it(logstream);

return 0;
}

I expect that at least the "Baz" line works for both std::cout and
log4cxx::logbase, and ideally the "Foo' line would too. At least for
the "Baz" case it occurs because log4cxx::logstream lacks typedefs a
la basic_ostream
(http://www.dinkumware.com/manuals/default.aspx?manual=compleat&page=ostream.html#basic_ostream).
I'm not sure if the "Foo" case could be made to work. If the "Baz"
case worked it might just require adding a template declarations to
log4cxx/stream.h that attempts to use the char_type and traits_type
typedef to fix the appropriate std::endl template.

Second, even if the first part did work, it seems that without the
magic log4cxx_base::endmsg manipulator that the messages are never
written. This is much less than generic, and I'd like to have
std::endl take the role of log4stream_base::endmsg whenever it is
encountered. From looking at Stroustrup's C++ programming language
section 21.4.6 I don't see how to intercept the single std::endl
manipulator and cause it to insert a log4stream_base::endmsg. I could
be missing something.

Any help appreciated,
Rhys

Re: How to build a x64 library on windows with Visual Studio?

2009-12-03T19:53:58Z

I do not believe that you should need to change any code. Been a while since I've tested a Win64 build, but I think the Ant driven VC++ build completed without issue. Don't recall the experience building within Visual Studio.

Likely a project file issue. The .vcproj file in the release is generated from the Ant build script, not Visual Studio, so it might be missing some features. You could likely generate an empty project file in Visual Studio and then copy the guts of the .vcproj in the release and it would resolve the issue.

_WIN32 is defined for all Windows builds including x86_64 and Itanium builds. _WIN64 is only defined for 64-bit builds. The only place you need to have _WIN64 is where the code differs between 64 and 32 bit Windows and in general that is usually places where the _WIN64 code would work with current 32-bit compilers but the 32-bit specific code will work with VC 6 and the like.

Re: How to build a x64 library on windows with Visual Studio?

2009-12-02T06:21:34Z

Hi Lars,

Thanks your response.

I have ported the log4cxx to a new VS2005 project which is defined to be x64 and build with APR, APR-util in the same solution. But I don't replace the WIN32 with WIN64 and still use the WIN32 on windows64 platform. Though I got some warning message when to build the APR libs, finally I build out the log4cxx dll. And used it in my application, so far it works well.

Thanks,

Tom

2009/12/2 Lars Schouw <schouwla@...>

By replacing WIN32 with WIN64 I mean that you need to

find all #ifdef WIN32 etc.. and replace them with #ifdef WIN64

From: Lars Schouw <schouwla@...>
To: Log4CXX User <log4cxx-user@...>
Sent: Wed, December 2, 2009 8:44:02 PM
Subject: Re: How to build a x64 library on windows with Visual Studio?

Hi Tom,

You need to open the solution in VS2008 and then select build -> Configuration manager. Then select new under active platform and choose to copy the win32 to x64. I the projects you need to replace WIN32 with WIN64. There might be more you need to do... that is a good start.

I assume is is the same under VS2005.

Lars

From: Zhou Tao <zhoutao109@...>
To: log4cxx-user@...
Sent: Fri, September 4, 2009 12:34:54 AM
Subject: How to build a x64 library on windows with Visual Studio?

Hi all,

I am trying to build the log4cxx libraries on a Windows x64 2003 server. I use a Visual Studio 2005 as the compiling tool.

I can build the APR, APR-UTIL with x64 option, however for log4cxx.dsp the x64 option in Visual Studio 2005 is disabled.

So how to use or build the log4cxx on a winx64 server.

Thanks tons,

Tom

--
Thanks and Regards,
Tom

Re: How to build a x64 library on windows with Visual Studio?

2009-12-02T03:50:52Z

By replacing WIN32 with WIN64 I mean that you need to

find all #ifdef WIN32 etc.. and replace them with #ifdef WIN64

From: Lars Schouw <schouwla@...>
To: Log4CXX User <log4cxx-user@...>
Sent: Wed, December 2, 2009 8:44:02 PM
Subject: Re: How to build a x64 library on windows with Visual Studio?

Hi Tom,

You need to open the solution in VS2008 and then select build -> Configuration manager. Then select new under active platform and choose to copy the win32 to x64. I the projects you need to replace WIN32 with WIN64. There might be more you need to do... that is a good start.

I assume is is the same under VS2005.

Lars

From: Zhou Tao <zhoutao109@...>
To: log4cxx-user@...
Sent: Fri, September 4, 2009 12:34:54 AM
Subject: How to build a x64 library on windows with Visual Studio?

Hi all,

I am trying to build the log4cxx libraries on a Windows x64 2003 server. I use a Visual Studio 2005 as the compiling tool.

I can build the APR, APR-UTIL with x64 option, however for log4cxx.dsp the x64 option in Visual Studio 2005 is disabled.

So how to use or build the log4cxx on a winx64 server.

Thanks tons,

Tom

Re: How to build a x64 library on windows with Visual Studio?

2009-12-02T03:44:02Z

Hi Tom,

I assume is is the same under VS2005.

Lars

From: Zhou Tao <zhoutao109@...>
To: log4cxx-user@...
Sent: Fri, September 4, 2009 12:34:54 AM
Subject: How to build a x64 library on windows with Visual Studio?

Hi all,

I am trying to build the log4cxx libraries on a Windows x64 2003 server. I use a Visual Studio 2005 as the compiling tool.

I can build the APR, APR-UTIL with x64 option, however for log4cxx.dsp the x64 option in Visual Studio 2005 is disabled.

So how to use or build the log4cxx on a winx64 server.

Thanks tons,

Tom

Re: Problems executing application with log4cxx

2009-11-24T04:23:34Z

The problem seems to be the size of log file, but now I have another problem.
If I want to use logger Sistema.RTEST, it doesn't work, but if I use
rootLooger, works fine.

SistemaRTEST4Cilindres.cpp

#include "SistemaRTEST4Cilindres.h"

LoggerPtr loggerSistemaRTEST(Logger::getLogger("Sistema.RTEST"));
//LoggerPtr loggerSistemaRTEST(Logger::getRootLogger());

void SistemaRTEST4Cilindres::obrirTargetes(){
LOG4CXX_INFO(loggerSistemaRTEST, "Abrimos los dispositivos para
las targetas que tenemos");
// EDITAR:
targetes[iE6229_1]->open("/dev/comedi0");
}
....
The only difference with other examples is that this code is inside a
directory.

main.cpp
Sistema/SistemaRTEST4Cilindres.h
Sistema/SistemaRTEST4Cilindres.cpp

I've tested in the main directoy and that worked correctly. That's
what I'm doing wrong?

Thank you

Quoting carlos_jimenez@...:

> Hello,
>
> First, sorry for my english.
>
> I'm new with log4cxx and I have problems. When I use
> PropertyConfiguration into my code, application crashes, but if I use
> BasicConfiguration, works fine.
>
> #include <log4cxx/logger.h>
> #include <log4cxx/propertyconfigurator.h>
> #include "Sistema/SistemaRTEST4Cilindres.h"
>
> using namespace log4cxx;
>
> LoggerPtr logger(Logger::getLogger("main"));
>
> int main(int argc, char *argv[]){
> SistemaRTEST4Cilindres *sistema=NULL;
>
> PropertyConfigurator::configure("/etc/rtai/log/log4cxx.properties");
>
> LOG4CXX_FATAL(logger, '\n');
> LOG4CXX_INFO(logger, "Programa main(): Cargamos el sistema");
>
> ....
>
>
> /etc/rtai/log/log4cxx.properties
>
> # Sample ResourceBundle properties file
> log4j.rootLogger=INFO, R
>
> log4j.appender.R=org.apache.log4j.RollingFileAppender
> log4j.appender.R.File=/var/log/rtaid.log
>
> log4j.appender.R.MaxFileSize=200KB
> log4j.appender.R.MaxBackupIndex=10
>
> log4j.appender.R.layout=org.apache.log4j.PatternLayout
> log4j.appender.R.layout.ConversionPattern=%d [%t] %-3p (%F:%L) - %m%n
>
> log4j.logger.Cicle=WARN
> log4j.logger.DadesFase=WARN
> log4j.logger.Fase=WARN
> log4j.logger.Modul=WARN
> log4j.logger.Sistema=WARN
> #log4j.logger.Sistema.RTEST=WARN
> log4j.logger.Transicions=WARN
> #log4j.logger.ServidorDades=WARN
>
>
> My host OS is Debian, someone have any idea??
>
> Thank you.
>
>
> --
> Carlos Jiménez
>
> ENCOPIM S.L.
> C/. del Parc 5 (nau 13), P.I. Els Pinetons
> E-08291 RIPOLLET (Barcelona)
> Tel: (+34) 935 94 23 47
> Fax: (+34) 935 94 64 15
>
> ==========================================================
> La información contenida en la presente transmisión es confidencial y su
> uso únicamente está permitido a su(s) destinatario(s). Si Ud. no es la
> persona destinataria de la presente transmisión, rogamos nos lo
> comunique de manera inmediata por teléfono (+34 935 942 347) y destruya
> cualquier copia de la misma (tanto digitales como en papel).
>
> The information contained in this transmission is confidential and is
> intended only for the use of the addressee(s). If you are not the
> designated recipient of this transmission, please advise us immediately
> by telephone (+34 935 942 347) and destroy any copies (digital and
> paper).
> ==========================================================

--
Carlos Jiménez

ENCOPIM S.L.
C/. del Parc 5 (nau 13), P.I. Els Pinetons
E-08291 RIPOLLET (Barcelona)
Tel: (+34) 935 94 23 47
Fax: (+34) 935 94 64 15

==========================================================
La información contenida en la presente transmisión es confidencial y su
uso únicamente está permitido a su(s) destinatario(s). Si Ud. no es la
persona destinataria de la presente transmisión, rogamos nos lo
comunique de manera inmediata por teléfono (+34 935 942 347) y destruya
cualquier copia de la misma (tanto digitales como en papel).

The information contained in this transmission is confidential and is
intended only for the use of the addressee(s). If you are not the
designated recipient of this transmission, please advise us immediately
by telephone (+34 935 942 347) and destroy any copies (digital and
paper).
==========================================================

Problems executing application with log4cxx

2009-11-24T04:05:43Z

Hello,

First, sorry for my english.

I'm new with log4cxx and I have problems. When I use
PropertyConfiguration into my code, application crashes, but if I use
BasicConfiguration, works fine.

#include <log4cxx/logger.h>
#include <log4cxx/propertyconfigurator.h>
#include "Sistema/SistemaRTEST4Cilindres.h"

using namespace log4cxx;

LoggerPtr logger(Logger::getLogger("main"));

int main(int argc, char *argv[]){
SistemaRTEST4Cilindres *sistema=NULL;

PropertyConfigurator::configure("/etc/rtai/log/log4cxx.properties");

LOG4CXX_FATAL(logger, '\n');
LOG4CXX_INFO(logger, "Programa main(): Cargamos el sistema");

....

/etc/rtai/log/log4cxx.properties

# Sample ResourceBundle properties file
log4j.rootLogger=INFO, R

log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=/var/log/rtaid.log

log4j.appender.R.MaxFileSize=200KB
log4j.appender.R.MaxBackupIndex=10

log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d [%t] %-3p (%F:%L) - %m%n

log4j.logger.Cicle=WARN
log4j.logger.DadesFase=WARN
log4j.logger.Fase=WARN
log4j.logger.Modul=WARN
log4j.logger.Sistema=WARN
#log4j.logger.Sistema.RTEST=WARN
log4j.logger.Transicions=WARN
#log4j.logger.ServidorDades=WARN

My host OS is Debian, someone have any idea??

Thank you.

--
Carlos Jiménez

ENCOPIM S.L.
C/. del Parc 5 (nau 13), P.I. Els Pinetons
E-08291 RIPOLLET (Barcelona)
Tel: (+34) 935 94 23 47
Fax: (+34) 935 94 64 15

==========================================================
La información contenida en la presente transmisión es confidencial y su
uso únicamente está permitido a su(s) destinatario(s). Si Ud. no es la
persona destinataria de la presente transmisión, rogamos nos lo
comunique de manera inmediata por teléfono (+34 935 942 347) y destruya
cualquier copia de la misma (tanto digitales como en papel).

The information contained in this transmission is confidential and is
intended only for the use of the addressee(s). If you are not the
designated recipient of this transmission, please advise us immediately
by telephone (+34 935 942 347) and destroy any copies (digital and
paper).
==========================================================

Re: LOG4CXX_DECODE_CHAR Crash on windows

2009-11-17T21:12:15Z

Thanks Curt,

My comments in line.

2009/11/18 Curt Arnold <carnold@...>

Mismatching run-time libraries is a easy way to manufacture a crash. Basically any time one DLL tries to deallocate some resource allocated by a DLL using a different run time library (and that includes two DLLs that each use /MT since they have the own instances of the run-time library), bad things will happen.

Tom>> Yes, it's the problem.

To build a DLL using the /MT run-time library and log4cxx, add the log4cxx source into your project and set the LOG4CXX_STATIC environment variable. If you try linking with a static library, you will only get the classes that you call directly. The ones that are expected to be present when the configuration is read will not have been linked into your DLL.

Tom>> Do you mean to build the log4cxx source into my DLL?
My context is to build the log4cxx to a DLL and the log4cxx DLL would be called in my DLL( build with /MT option). Mostly I cannot combine the log4cxx code with my DLL code together. I maybe misunderstand you about your way to handle the issue.

Regards,
Tom

--
Thanks and Regards,
Tom

Re: LOG4CXX_DECODE_CHAR Crash on windows

2009-11-17T19:29:15Z

Mismatching run-time libraries is a easy way to manufacture a crash.
Basically any time one DLL tries to deallocate some resource allocated
by a DLL using a different run time library (and that includes two
DLLs that each use /MT since they have the own instances of the run-
time library), bad things will happen.

To build a DLL using the /MT run-time library and log4cxx, add the
log4cxx source into your project and set the LOG4CXX_STATIC
environment variable. If you try linking with a static library, you
will only get the classes that you call directly. The ones that are
expected to be present when the configuration is read will not have
been linked into your DLL.

Re: LOG4CXX_DECODE_CHAR Crash on windows

2009-11-17T00:39:12Z

I take a look at the problem. The issue is caused by using mixed MT/MD option in one process. My DLL is using MT option and log4cxx is using MD, so they are using different copy of CRT lib. I call the LOG4CXX_DECODE_CHAR macro within my DLL to create a LogString variable then get the fail. ( note: in debug mode on windows32).

Macro:

#define LOG4CXX_DECODE_CHAR(var, src) \

log4cxx::LogString var; \

log4cxx::helpers::Transcoder::decode(src, var)

I check the Transcoder::decode(const std::string& src, LogString& dst) function,

dst.reserve(dst.size()+src.size());

The above statement maybe allocate new bytes in the CRT heap used by log4cxx, but the dst variable would be freed in my DLL if I use the macro. The two DLLs have two different copy of CRT libs. So cause a heap corruption error.

I understand if all DLLs are build with MD option, then OK.

So my question is,

1. the macro LOG4CXX_DECODE_CHAR(var, src) is only used for log4cxx DLL internally?

2. Why not to only fill the memory in decode function, but not to change the size of the passed-in CRT objects? It's a rule I often use. I mean to change the size of dst object some where outside of the decode function.

3. Is it possible to create other ways to generate a logstring based on the std::string content?

Thanks,

Tom

2009/11/13 Zhou Tao <zhoutao109@...>

Hi all,

I am using log4cxx on win32 platform and build the log4cxx with MT option( Runtime Library) within MS visual Studio 2005. The project default setting is MD. All APR, APR-UTIL and LOG4CXX projects are set to be MT mode.

After the build, I get a crash in the LOG4CXX_DECODE_CHAR macro. The code is very simple, looks like the below,

void testFun()
{
std::string src = "log4cxx-string-testing";
LOG4CXX_DECODE_CHAR(dest, src);
}

The crash happens when leave the function when trying to delete the allocated memory. If the length of the src string is less than 7, it works.

Is this a problem?

--
Thanks and Regards,
Tom

--
Thanks and Regards,
Tom

Re: Compilation Error -Log4cxx 0.10.0 on AS3 Redhat Linux (gcc2.96)]

2009-11-15T19:56:15Z

When I checked the archives, it appears that you have reported this
before. From log4cxx-user in July 12, 2008 I replied:
>
> gcc 2.96 was a prerelease version of gcc 3.x and has an incomplete
> implementation of the C++ Standard Template Library (see http://gcc.gnu.org/gcc-2.96.html
> ) . I have been able to get messagebuffer.h to compile by forward
> declaring std::ios_base and replacing std::basic_ostream<char> with
> std::ostream and similar changes, but there are also compilation
> failures in cachedateformat.cpp and properties.h and there may be
> others. I do not intend to work around gcc 2.96's limitation.
>

gcc 2.96 is an odd-ball compiler disavowed by the gcc team. I'm not
saying that I'd be opposed to integrating patches to work around its
limitations as long as it doesn't compromise current and/or standard
compliant compilers. However, there is nothing that motivates me to
work through the issues with this compiler for you.

Compilation Error -Log4cxx 0.10.0 on AS3 Redhat Linux (gcc2.96)]

2009-11-13T02:30:15Z

I am able to compile apr, aprutil and successfully generated the libraries.

When I try to make log4cxx libraries, getting the following error.

Errors:
1. src/main/include/log4cxx/helpers/messagebuffer.h:158: `::basic_ostream'
undeclared (first use here)
2. src/main/include/log4cxx/helpers/messagebuffer.h:194:
`CharMessageBuffer' was not declared in this scope
3. src/main/include/log4cxx/helpers/messagebuffer.h:194: `os' was not
declared in this scope
4. src/main/include/log4cxx/helpers/messagebuffer.h:194:
`log4cxx::helpers::operator<< (...)' must have an argument of class or
enumerated type
5. /src/main/include/log4cxx/helpers/messagebuffer.h:195: `val' undeclared
6. /src/main/include/log4cxx/logger.h:44: `LoggerRepository' was not
declared in this scope

Any suggestions please.

Regards
SrkRaju

______________________________________________________________________________

DISCLAIMER

The information contained in this e-mail message and/or attachments to it may
contain confidential or privileged information. If you are not the intended
recipient, any dissemination, use, review, distribution, printing or copying
of the information contained in this e-mail message and/or attachments to it
are strictly prohibited. If you have received this communication in error,
please notify us by reply e-mail or directly to netsupport@... or
telephone and immediately and permanently delete the message and any
attachments. Thank you.

______________________________________________________________________________

This email has been scrubbed for your protection by SecureMX.
For more information visit http://securemx.in
______________________________________________________________________________

--
Thanks& Regards,
S. Ramakrishna Raju
phone: 919441432458

LOG4CXX_DECODE_CHAR Crash on windows

2009-11-13T01:56:47Z

Hi all,

I am using log4cxx on win32 platform and build the log4cxx with MT option( Runtime Library) within MS visual Studio 2005. The project default setting is MD. All APR, APR-UTIL and LOG4CXX projects are set to be MT mode.

After the build, I get a crash in the LOG4CXX_DECODE_CHAR macro. The code is very simple, looks like the below,

void testFun()
{
std::string src = "log4cxx-string-testing";
LOG4CXX_DECODE_CHAR(dest, src);
}

The crash happens when leave the function when trying to delete the allocated memory. If the length of the src string is less than 7, it works.

Is this a problem?

--
Thanks and Regards,
Tom

Re: problem with install log4cxx

2009-11-12T20:40:17Z

On Nov 10, 2009, at 4:52 AM, Bajramovic, Ervin wrote:

> Hi everybody
>
> I want to build log4cxx
>
> I used the following configuration:
>
> ./autogen.sh
>
> ./configure CFLAGS="-O2 -s -mms-bitfields -march=i686" CXXFLAGS="-O2
> -s -mms-bitfields -march=i686" --with-apr=/usr/local --with-apr-
> util=/usr/local
>
> make && make install
>
> And i get this error:

...
> test -z "/usr/local/include/log4cxx/private" || /bin/mkdir -p "/usr/
> local/include/log4cxx/private"
> /bin/install -c -m 644 ../../../../../src/main/include/log4cxx/
> private/log4cxx_private.h log4cxx_private.h '/usr/local/include/
> log4cxx/private'
> /bin/install: will not overwrite just-created `/usr/local/include/
> log4cxx/private/log4cxx_private.h' with `log4cxx_private.h'
> make[6]: *** [install-privateincHEADERS] Error 1

Since you are failing to write to /usr/local, I'm guessing it is a
permissions issue and you need to do "sudo make install" or the
equivalent.

problem with install log4cxx

2009-11-10T02:52:12Z

Hi everybody

I want to build log4cxx

I used the following configuration:

./autogen.sh

./configure CFLAGS="-O2 -s -mms-bitfields -march=i686" CXXFLAGS="-O2 -s -mms-bitfields -march=i686" --with-apr=/usr/local --with-apr-util=/usr/local

make && make install

And i get this error:

Making install in db

make[5]: Entering directory `/home/lab409/log4cxx/src/main/include/log4cxx/db'

make[6]: Entering directory `/home/lab409/log4cxx/src/main/include/log4cxx/db'

make[6]: Nothing to be done for `install-exec-am'.

test -z "/usr/local/include/log4cxx/db" || /bin/mkdir -p "/usr/local/include/log4cxx/db"

/bin/install -c -m 644 ../../../../../src/main/include/log4cxx/db/odbcappender.h '/usr/local/include/log4cxx/db'

make[6]: Leaving directory `/home/lab409/log4cxx/src/main/include/log4cxx/db'

make[5]: Leaving directory `/home/lab409/log4cxx/src/main/include/log4cxx/db'

Making install in private

make[5]: Entering directory `/home/lab409/log4cxx/src/main/include/log4cxx/private'

make[6]: Entering directory `/home/lab409/log4cxx/src/main/include/log4cxx/private'

make[6]: Nothing to be done for `install-exec-am'.

test -z "/usr/local/include/log4cxx/private" || /bin/mkdir -p "/usr/local/include/log4cxx/private"

/bin/install -c -m 644 ../../../../../src/main/include/log4cxx/private/log4cxx_private.h log4cxx_private.h '/usr/local/include/log4cxx/private'

/bin/install: will not overwrite just-created `/usr/local/include/log4cxx/private/log4cxx_private.h' with `log4cxx_private.h'

make[6]: *** [install-privateincHEADERS] Error 1

make[6]: Leaving directory `/home/lab409/log4cxx/src/main/include/log4cxx/private'

make[5]: *** [install-am] Error 2

make[5]: Leaving directory `/home/lab409/log4cxx/src/main/include/log4cxx/private'

make[4]: *** [install-recursive] Error 1

make[4]: Leaving directory `/home/lab409/log4cxx/src/main/include/log4cxx'

make[3]: *** [install-recursive] Error 1

make[3]: Leaving directory `/home/lab409/log4cxx/src/main/include'

make[2]: *** [install-recursive] Error 1

make[2]: Leaving directory `/home/lab409/log4cxx/src/main'

make[1]: *** [install-recursive] Error 1

make[1]: Leaving directory `/home/lab409/log4cxx/src'

make: *** [install-recursive] Error 1

I tested it with the packe from the apache download mirror Log4cxx-0.10.0

and with de svn source from svn.apache.org/repos/asf/logging/log4cxx/trunk/

Asf - Revision 834383 and got the same error.

Can enybody tell mi how to fix it

Ervin Bajramovic

________________________________

DISCLAIMER :
This e-mail is for the intended recipient only
If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited.
If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.

Re: Memory Leak with MFC

2009-11-08T16:48:59Z

thanks Patrick, Cory,

I've understood that these are not memory leak.
They are side effects of ordering of destruction.
and I ran my sample program 3 times.
the allocation numbers are consistent.

> Patrick is right. Run it a few times and see if the allocation numbers
> change (124, 1151, and 1152). If you can get it to repeat consistently,
> set a breakpoint at those allocations to see what it is that's leaking.
>
> You could also rebuild using the debug version of new. That way, you
> will get file and line numbers in the memory dumps.
>
> -cory
>
>
> Griffiths, Patrick wrote:
>> This doesn't show that the leak is or is not log4cxx.
>>
>> Keep in mind that log4cxx uses static singleton objects. It's quite possible that what you are seeing is a simply a side effect caused by the ordering of the destruction of static objects.
>>
>> -----Original Message-----
>> From: "山脇健一(Yamawaki Kenichi)" [mailto:k-yamawaki@...]
>> Sent: Wednesday, November 04, 2009 5:23 PM
>> To: log4cxx-user@...
>> Subject: Memory Leak with MFC
>>
>> Hi Exparts,
>>
>> I use the log4cxx-0.10.0.
>> I made below programs with MFC. Then I have faced a certain memory leak.
>> Please teach the method of settlement.
>>
>> // leak version (with MFC)
>> BOOL CLogTestDlg::OnInitDialog()
>> {
>> CDialog::OnInitDialog();
>> LoggerPtr logger = Logger::getLogger( "test" );
>> return TRUE;
>> }
>>
>> -----------------------------------------------------------------
>> Detected memory leaks!
>> Dumping objects ->
>> {1152} normal block at 0x01B08818, 56 bytes long.
>> Data: <0 n 0 n 0 n > 30 F1 6E 02 30 F1 6E 02 30 F1 6E 02 00 00 00 00
>> {1151} normal block at 0x01B08768, 116 bytes long.
>> Data: <Lb db -n > 4C 62 1D 10 64 62 1D 10 8C 2D 6E 02 00 00 00 00
>>
>> -----Omission ------
>>
>> {124} normal block at 0x01B02218, 52 bytes long.
>> Data: < P l P > C8 50 B0 01 90 6C B0 01 50 BA B0 01 CD CD CD CD
>> -----------------------------------------------------------------
>>
>> // A program without MFC doesn't leak memory.
>> int _tmain(int argc, _TCHAR* argv[])
>> {
>> LoggerPtr logger = Logger::getLogger("test");
>> return 0;
>> }
>>
>> thanks,
>> Kenichi
>>
>>
>>
>>
>> This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.
>>
>>
>>
>
>

--
Kenichi Yamawaki
carina system co.,ltd.
E-mail:k-yamawaki@...
TEL +81-78-954-5231

Re: Memory Leak with MFC

2009-11-05T07:32:56Z

Patrick is right. Run it a few times and see if the allocation numbers
change (124, 1151, and 1152). If you can get it to repeat consistently,
set a breakpoint at those allocations to see what it is that's leaking.

You could also rebuild using the debug version of new. That way, you
will get file and line numbers in the memory dumps.

-cory

Griffiths, Patrick wrote:

> This doesn't show that the leak is or is not log4cxx.
>
> Keep in mind that log4cxx uses static singleton objects. It's quite possible that what you are seeing is a simply a side effect caused by the ordering of the destruction of static objects.
>
> -----Original Message-----
> From: "山脇健一(Yamawaki Kenichi)" [mailto:k-yamawaki@...]
> Sent: Wednesday, November 04, 2009 5:23 PM
> To: log4cxx-user@...
> Subject: Memory Leak with MFC
>
> Hi Exparts,
>
> I use the log4cxx-0.10.0.
> I made below programs with MFC. Then I have faced a certain memory leak.
> Please teach the method of settlement.
>
> // leak version (with MFC)
> BOOL CLogTestDlg::OnInitDialog()
> {
> CDialog::OnInitDialog();
> LoggerPtr logger = Logger::getLogger( "test" );
> return TRUE;
> }
>
> -----------------------------------------------------------------
> Detected memory leaks!
> Dumping objects ->
> {1152} normal block at 0x01B08818, 56 bytes long.
> Data: <0 n 0 n 0 n > 30 F1 6E 02 30 F1 6E 02 30 F1 6E 02 00 00 00 00
> {1151} normal block at 0x01B08768, 116 bytes long.
> Data: <Lb db -n > 4C 62 1D 10 64 62 1D 10 8C 2D 6E 02 00 00 00 00
>
> -----Omission ------
>
> {124} normal block at 0x01B02218, 52 bytes long.
> Data: < P l P > C8 50 B0 01 90 6C B0 01 50 BA B0 01 CD CD CD CD
> -----------------------------------------------------------------
>
> // A program without MFC doesn't leak memory.
> int _tmain(int argc, _TCHAR* argv[])
> {
> LoggerPtr logger = Logger::getLogger("test");
> return 0;
> }
>
> thanks,
> Kenichi
>
>
>
>
> This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.
>
>
>

RE: Memory Leak with MFC

2009-11-05T06:39:40Z

This doesn't show that the leak is or is not log4cxx.

Keep in mind that log4cxx uses static singleton objects. It's quite possible that what you are seeing is a simply a side effect caused by the ordering of the destruction of static objects.

-----Original Message-----
From: "山脇健一(Yamawaki Kenichi)" [mailto:k-yamawaki@...]
Sent: Wednesday, November 04, 2009 5:23 PM
To: log4cxx-user@...
Subject: Memory Leak with MFC

Hi Exparts,

I use the log4cxx-0.10.0.
I made below programs with MFC. Then I have faced a certain memory leak.
Please teach the method of settlement.

// leak version (with MFC)
BOOL CLogTestDlg::OnInitDialog()
{
CDialog::OnInitDialog();
LoggerPtr logger = Logger::getLogger( "test" );
return TRUE;
}

-----------------------------------------------------------------
Detected memory leaks!
Dumping objects ->
{1152} normal block at 0x01B08818, 56 bytes long.
Data: <0 n 0 n 0 n > 30 F1 6E 02 30 F1 6E 02 30 F1 6E 02 00 00 00 00
{1151} normal block at 0x01B08768, 116 bytes long.
Data: <Lb db -n > 4C 62 1D 10 64 62 1D 10 8C 2D 6E 02 00 00 00 00

-----Omission ------

{124} normal block at 0x01B02218, 52 bytes long.
Data: < P l P > C8 50 B0 01 90 6C B0 01 50 BA B0 01 CD CD CD CD
-----------------------------------------------------------------

// A program without MFC doesn't leak memory.
int _tmain(int argc, _TCHAR* argv[])
{
LoggerPtr logger = Logger::getLogger("test");
return 0;
}

thanks,
Kenichi

This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.

Memory Leak with MFC

2009-11-04T16:23:02Z

Hi Exparts,

I use the log4cxx-0.10.0.
I made below programs with MFC. Then I have faced a certain memory leak.
Please teach the method of settlement.

// leak version (with MFC)
BOOL CLogTestDlg::OnInitDialog()
{
CDialog::OnInitDialog();
LoggerPtr logger = Logger::getLogger( "test" );
return TRUE;
}

-----------------------------------------------------------------
Detected memory leaks!
Dumping objects ->
{1152} normal block at 0x01B08818, 56 bytes long.
Data: <0 n 0 n 0 n > 30 F1 6E 02 30 F1 6E 02 30 F1 6E 02 00 00 00 00
{1151} normal block at 0x01B08768, 116 bytes long.
Data: <Lb db -n > 4C 62 1D 10 64 62 1D 10 8C 2D 6E 02 00 00 00 00

-----Omission ------

{124} normal block at 0x01B02218, 52 bytes long.
Data: < P l P > C8 50 B0 01 90 6C B0 01 50 BA B0 01 CD CD CD CD
-----------------------------------------------------------------

// A program without MFC doesn't leak memory.
int _tmain(int argc, _TCHAR* argv[])
{
LoggerPtr logger = Logger::getLogger("test");
return 0;
}

thanks,
Kenichi

ant build options not working on Windows? (unichar, wchar_t, etc)

2009-10-29T23:14:29Z

Hi,

I'm tangling with log4cxx and going under...

I'm on Windows XP and using MSVC9 and used the following:
- apache-log4cxx-0.10.0.tar.gz
- apr-util-1.2.12.tar.gz (the latest didn't work,
can't remember the reason)
- apr-1.2.12.tar.gz (same again, latest
version didn't work)
- cpptasks-1.0b5 (and built cpptasks.jar using ant)
- ant-contrib-1.0b5-bin (came with ant-contrib-1.0b3.jar)

(ant couldn't find tools.jar either. I 'solved' this by copying it
from the jdk/lib int jre/lib too, probably should've fixed paths or
something but ...)

Sorry for the long post. Please pick it apart and just answer what you
can or want. Thanks heaps for any help!

So to begin, I have log4cxx building via ant:

$ant -Dfind=false

The library files are built and passes most but not all tests. I've
used it and it is logging. Fine. Great. Okay...

If I want to modify the build options, do I use the command line args
(-D...) or modify log4cxx.hw? The former doesn't seem to be working
for me. That is, when I modify the build options, say
-Denable-wchar_t=yes, they don't seem to effect the generated
log4cxx.h.

So, if I run:
$ant -Dfind=false -Denable-wchar_t=yes -Denable-unichar=yes
-Dwith-logchar=wchar_t

generates the log4cxx.h as:
#define LOG4CXX_LOGCHAR_IS_UTF8 0
#if LOG4CXX_LOGCHAR_IS_UTF8
#define LOG4CXX_LOGCHAR_IS_WCHAR 0
#else
#define LOG4CXX_LOGCHAR_IS_WCHAR 1
#endif
#define LOG4CXX_LOGCHAR_IS_UNICHAR 0

#define LOG4CXX_CHAR_API 1
#define LOG4CXX_WCHAR_T_API 1
#define LOG4CXX_UNICHAR_API 0
#define LOG4CXX_CFSTRING_API 0

Why isn't LOG4CXX_UNICHAR_API = 1? What isn't
LOG4CXX_LOGCHAR_IS_UNICHAR = 1? Does it not make sense to have both
wchar_t and unichar enabled?

So, if I run:
$ant -Dfind=false -Denable-wchar_t=no -Denable-unichar=yes
-Dwith-logchar=unichar

#define LOG4CXX_LOGCHAR_IS_UTF8 0
#if LOG4CXX_LOGCHAR_IS_UTF8
#define LOG4CXX_LOGCHAR_IS_WCHAR 0
#else
#define LOG4CXX_LOGCHAR_IS_WCHAR 1
#endif
#define LOG4CXX_LOGCHAR_IS_UNICHAR 0

#define LOG4CXX_CHAR_API 1
#define LOG4CXX_WCHAR_T_API 1
#define LOG4CXX_UNICHAR_API 0
#define LOG4CXX_CFSTRING_API

No change.

So, now to try and use UTF8 and no wide characters:
$ant -Dfind=false -Denable-wchar_t=no -Denable -Dwith-logchar=utf-8

#define LOG4CXX_LOGCHAR_IS_UTF8 0
#if LOG4CXX_LOGCHAR_IS_UTF8
#define LOG4CXX_LOGCHAR_IS_WCHAR 0
#else
#define LOG4CXX_LOGCHAR_IS_WCHAR 1
#endif
#define LOG4CXX_LOGCHAR_IS_UNICHAR 0

#define LOG4CXX_CHAR_API 1
#define LOG4CXX_WCHAR_T_API 1
#define LOG4CXX_UNICHAR_API 0
#define LOG4CXX_CFSTRING_API

Again, no change.

So I've been modifying log4cxx.hw. I seem to have wchar_t and utf-8
working independently. Can these be compiled into the same shared
library? Or do I need separate ones? And how should I handle the
modified header log4cxx.h when putting it into a dependency / 3rd
party folder? I.e., two includes folders?

However, back to the build. When I set the following, I get many
errors (can post if needed):
#define LOG4CXX_LOGCHAR_IS_UTF8 0
#if LOG4CXX_LOGCHAR_IS_UTF8
#define LOG4CXX_LOGCHAR_IS_WCHAR 0
#else
#define LOG4CXX_LOGCHAR_IS_WCHAR 0
#endif
#define LOG4CXX_LOGCHAR_IS_UNICHAR 1

#define LOG4CXX_CHAR_API 0
#define LOG4CXX_WCHAR_T_API 0
#define LOG4CXX_UNICHAR_API 1
#define LOG4CXX_CFSTRING_API

These are reduced when I include the char and wchar APIs...
#define LOG4CXX_LOGCHAR_IS_UTF8 0
#if LOG4CXX_LOGCHAR_IS_UTF8
#define LOG4CXX_LOGCHAR_IS_WCHAR 0
#else
#define LOG4CXX_LOGCHAR_IS_WCHAR 0
#endif
#define LOG4CXX_LOGCHAR_IS_UNICHAR 1

#define LOG4CXX_CHAR_API 1
#define LOG4CXX_WCHAR_T_API 1
#define LOG4CXX_UNICHAR_API 1
#define LOG4CXX_CFSTRING_API

...to:
- ndc.cpp(265) : error C2039: 'message' : is not a member of
'std::pair<_Ty1,_Ty2>'
- ndc.cpp(282) : error C2039: 'message' : is not a member of
'std::pair<_Ty1,_Ty2>'
- transcoder.cpp(35) : fatal error C1083: Cannot open include file:
'CoreFoundation/CFString.h': No such file or directory.

I looked at ndc.cpp and hacked / changed both lines 265 & 282 from:
Transcoder::encode(stack.top().message, dst);
to:
Transcoder::encode(getMessage(stack.top()), dst);

I had no idea and didn't look into it but it compiled; I was desperate.

But the second error is not hackable. Why is CoreFoundation required?

#if LOG4CXX_LOGCHAR_IS_UNICHAR || LOG4CXX_CFSTRING_API || LOG4CXX_UNICHAR_API
#include <CoreFoundation/CFString.h>
#endif

What I have I misunderstood?

The following doesn't complain (compile or run-time) but it the
characters appears as question marks in the output:
LOG4CXX_DEBUG(logger, LOG4CXX_STR("the message u30A8\u30FC\u30B8\u30A7"))

I guess it is something to do with the "with-charset" but I can't
modify the build options (-Dwith-charset) and I don't know where else
to modify this...

Again, sorry for the long post. Hopefully it makes sense - it is a
Friday night after all.

Cheers,
Sam

Building log4cxx

2009-10-22T17:19:05Z

Hello All,

I am building log4cxx using Makefile. Everything works fine. I have one question though.
I am trying to write my own appender. This appender uses axis2c libraries. I put my appender in log4cxx src and building. But since my appender uses axis2C libraries, I need to link axis2C libraries to log4cxx while building.

I tried adding libraries in Makefile (LDFLAGS ). But its not working.

Could some point me in the right direction.

Thanks
Vinay

On Thu, Oct 22, 2009 at 11:18 AM, Moshe Matitya <Moshe.Matitya@...> wrote:

I have been trying, unsuccessfully, to figure out how to install log4cxx on Linux with Ant.

In the past, when installing log4cxx 0.9.7 on a Linux machine, I would build and install it using Make, as follows: To build it, I would run the following commands:

            autogen.sh

            configure

            make

Then, to install it, I would simply run:

            make install

This would install all the library files, include files, etc., in their proper locations.

Now, however, I am using log4cxx 0.10.0, which I build using Ant. The default target in the Ant build script compiles and links the sources, and runs the unit tests. However, I don't see how one is supposed to then install it, and I can't find any instructions about how to do this in the documentation.

There doesn't seem to be a target in the Ant build script called "install", or anything similar. So how does one install log4cxx when using Ant?

Thanks,

Moshe Z. Matitya

XConnect Global Networks

RE: Installing log4cxx on Linux with Ant

2009-10-22T13:16:04Z

No, not really. install-sh is not a script for installing log4cxx, it's just a general utility that does little more than copy a specified file from one place to another. In order to use install-sh to install log4cxx, I'd first need to know exactly which files are supposed to be installed, and where. This information is not documented anywhere that I know of. And if I were to take the time and trouble to figure out that information, then install-sh would provide very little advantage over simply using cp and chmod.

It seems to me that there ought to be some way to install log4cxx using Ant, just like there is with Make. I can't be the first person who's run into this problem. How does everyone else install log4cxx on Linux/Unix?

Moshe

From: Cory Riddell [cory@...]
Sent: Thursday, October 22, 2009 8:30 PM
To: Log4CXX User
Subject: Re: Installing log4cxx on Linux with Ant

Does the install-sh script do what you want?

Moshe Matitya wrote:

I have been trying, unsuccessfully, to figure out how to install log4cxx on Linux with Ant.

In the past, when installing log4cxx 0.9.7 on a Linux machine, I would build and install it using Make, as follows: To build it, I would run the following commands:

            autogen.sh

            configure

            make

Then, to install it, I would simply run:

            make install

This would install all the library files, include files, etc., in their proper locations.

Now, however, I am using log4cxx 0.10.0, which I build using Ant. The default target in the Ant build script compiles and links the sources, and runs the unit tests. However, I don't see how one is supposed to then install it, and I can't find any instructions about how to do this in the documentation.

There doesn't seem to be a target in the Ant build script called "install", or anything similar. So how does one install log4cxx when using Ant?

Thanks,

Moshe Z. Matitya

XConnect Global Networks

Re: Installing log4cxx on Linux with Ant

2009-10-22T11:30:20Z

Does the install-sh script do what you want?

Moshe Matitya wrote:

I have been trying, unsuccessfully, to figure out how to install log4cxx on Linux with Ant.

In the past, when installing log4cxx 0.9.7 on a Linux machine, I would build and install it using Make, as follows: To build it, I would run the following commands:

            autogen.sh

            configure

            make

Then, to install it, I would simply run:

            make install

This would install all the library files, include files, etc., in their proper locations.

Now, however, I am using log4cxx 0.10.0, which I build using Ant. The default target in the Ant build script compiles and links the sources, and runs the unit tests. However, I don't see how one is supposed to then install it, and I can't find any instructions about how to do this in the documentation.

There doesn't seem to be a target in the Ant build script called "install", or anything similar. So how does one install log4cxx when using Ant?

Thanks,

Moshe Z. Matitya

XConnect Global Networks

Installing log4cxx on Linux with Ant

2009-10-22T11:18:35Z

I have been trying, unsuccessfully, to figure out how to install log4cxx on Linux with Ant.

In the past, when installing log4cxx 0.9.7 on a Linux machine, I would build and install it using Make, as follows: To build it, I would run the following commands:

autogen.sh

configure

make

Then, to install it, I would simply run:

make install

This would install all the library files, include files, etc., in their proper locations.

Now, however, I am using log4cxx 0.10.0, which I build using Ant. The default target in the Ant build script compiles and links the sources, and runs the unit tests. However, I don't see how one is supposed to then install it, and I can't find any instructions about how to do this in the documentation.

There doesn't seem to be a target in the Ant build script called "install", or anything similar. So how does one install log4cxx when using Ant?

Thanks,

Moshe Z. Matitya

XConnect Global Networks

Re: Build fail on AIX using XLC compiler

2009-10-20T01:17:23Z

Experts,

I looked through the simpledateformat.h header file and made the below change and the build of simpledateformat.cpp passed. It looks like the below syntax to use the std::locale class causes the problem when enable the -D_LARGE_FILES compiler flag for AIX XLC.

change the below:

namespace std { class locale; }

to be:

using std::locale;

or to be:

#if LOG4CXX_HAS_STD_LOCALE
#include <locale>
#endif

Then the build of simpledateformat.cpp succeed. Is there some reason to use the std::locale this way? To support multi-platforms? Or someone could provide a formal fix based on my change?

BTW, my building env:

CC = xlc_r

CXX = xlC_r

CFLAGS = -q64 -D_LARGE_FILES -qarch=ppc64 -qsmp

CXXFLAGS= -q64 -D_LARGE_FILES -qarch=ppc64 -qsmp -qpic=large

LDFLAGS = -q64 -qsmp -brtl -bbigtoc

Thanks,

Tom

2009/9/29 Zhou Tao <zhoutao109@...>

Hi all,

I am building log4cxx on AIX using XLC as the compiler. And I turn on the -D_LARGE_FILES compiler flag for our purpose. However seems that log4cxx dislikes the compiler flag. I could build APR, APR-UTIL and when I build log4cxx, errors happen when build the simpledateformat.cpp file. The error message is the following,

/bin/sh ../../../libtool --tag=CXX --mode=compile /usr/vacpp/bin/xlC_r -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"log4cxx\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_MBSRTOWCS=1 -DHAVE_WCSTOMBS=1 -DHAVE_SYSLOG=1 -DHAVE_FWIDE=1 -I. -I. -I../../../src/main/include -I../../../src/main/include -I/usr/vacpp/include -U__STR__ -D_THREAD_SAFE -D_USE_IRS -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr/include/apr-1 -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr-util/include/apr-1 -q64 -D_LARGE_FILES -qlonglong -c -o simpledateformat.lo simpledateformat.cpp
/usr/vacpp/bin/xlC_r -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"log4cxx\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_MBSRTOWCS=1 -DHAVE_WCSTOMBS=1 -DHAVE_SYSLOG=1 -DHAVE_FWIDE=1 -I. -I. -I../../../src/main/include -I../../../src/main/include -I/usr/vacpp/include -U__STR__ -D_THREAD_SAFE -D_USE_IRS -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr/include/apr-1 -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr-util/include/apr-1 -q64 -D_LARGE_FILES -qlonglong -c -M simpledateformat.cpp -DPIC -o .libs/simpledateformat.o
"simpledateformat.cpp", line 735.15: 1540-1118 (S) The declaration of "defaultLocale" uses the undefined class "std::locale" when the class must be complete.
"simpledateformat.cpp", line 124.25: 1540-0218 (S) The call does not match any parameter list for "std::has_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >".
"/usr/vacpp/include/locale", line 194.14: 1540-1283 (I) "std::_LFS_ON::has_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 124.35: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
"simpledateformat.cpp", line 125.63: 1540-0218 (S) The call does not match any parameter list for "std::use_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >".
"/usr/vacpp/include/xlocale", line 293.19: 1540-1283 (I) "std::_LFS_ON::use_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 125.73: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
"simpledateformat.cpp", line 136.25: 1540-0218 (S) The call does not match any parameter list for "std::has_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >".
"/usr/vacpp/include/locale", line 194.14: 1540-1283 (I) "std::_LFS_ON::has_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 136.35: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
"simpledateformat.cpp", line 137.60: 1540-0218 (S) The call does not match any parameter list for "std::use_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >".
"/usr/vacpp/include/xlocale", line 293.19: 1540-1283 (I) "std::_LFS_ON::use_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 137.70: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
make[3]: *** [simpledateformat.lo] Error 1

Any insight for this issue is greatly appreciated.
Tom

--
Thanks and Regards,
Tom

Re: How to clean up the log4cxx objects to avoid the memory leak?

2009-10-14T03:55:20Z

Hi Tom,

You dont need to reclaim the memory, smart pointer will do it automatically once it goes out of scope.

LoggerPtr is a typedef for helpers::ObjectPtrT<Logger>. The class

ObjectPtr is a Smart Pointer pattern implementation, which uses the

helper class ObjectImpl. This class uses apr_atomic_inc32 and

apr_atomic_dec32 to count the references to itself. If the reference

count is 0, it deletes itself.

You can validate it by running any memory profiler on your code.

Thanks

Deepak

On Wed, Oct 14, 2009 at 1:50 PM, Zhou Tao <zhoutao109@...> wrote:

Thanks, Deepak

So if want to close one created looger and release its releated resources, what should I do? using smart pointer, I don't need to delete the objects.

But How can I release the resources? Do I need to call the below API to release the resources?

//close the appender

_appenderPtr->close();

//close all appenders associated with the logger

_loggerPtr->closeNestedAppenders();

_loggerPtr->removeAllAppenders();

Or some other APIs I need to call to release all resources to avoid memory leak?

Thank you.
2009/10/14 deepak singh <deepak.iitg@...>
You should use smart pointer instead.
e.g
    log4cxx::LogManager::resetConfiguration(); 



   log4cxx::LayoutPtr layoutPtr(new log4cxx::PatternLayout("%c-%p (%d{dd MMM yyyy HH:mm:ss}) [%-5t] %m%n")); 


   log4cxx::AppenderPtr appenderPtr( new log4cxx::ConsoleAppender(layoutPtr, "System.err")); 
   log4cxx::BasicConfigurator::configure(appenderPtr);
Thanks
Deepak

On Wed, Oct 14, 2009 at 8:41 AM, Zhou Tao <zhoutao109@...> wrote:

Experts,

I am using the log4cxx-0.10.0. And at the begining of the application, I create the log4cxx instances including Logger, FileAppender, PatternLayout etc. Sometime within the application, I need to destroy the instances.

For example,

To create the below objects at the begining,

_layout = new log4cxx::PatternLayout(format);

_fileAppender = new log4cxx::RollingFileAppender();

....

Then somewhere to remove the above objects like the below,

delete _fileAppender;

delete _layout;

....

However when deleting the objects, always core dump on windows. On unix, when the application exit, also get a core dump.

Then how to clean up the log4cxx instances or a sequence is required when deleting the objects? or some example code?

Any suggestion are highly appreciated.

Thanks,

Tom

Re: How to clean up the log4cxx objects to avoid the memory leak?

2009-10-14T01:20:49Z

Thanks, Deepak

So if want to close one created looger and release its releated resources, what should I do? using smart pointer, I don't need to delete the objects.

But How can I release the resources? Do I need to call the below API to release the resources?

//close the appender

_appenderPtr->close();

//close all appenders associated with the logger

_loggerPtr->closeNestedAppenders();

_loggerPtr->removeAllAppenders();

Or some other APIs I need to call to release all resources to avoid memory leak?

Thank you.

2009/10/14 deepak singh <deepak.iitg@...>

You should use smart pointer instead.
e.g
    log4cxx::LogManager::resetConfiguration(); 


   log4cxx::LayoutPtr layoutPtr(new log4cxx::PatternLayout("%c-%p (%d{dd MMM yyyy HH:mm:ss}) [%-5t] %m%n")); 

   log4cxx::AppenderPtr appenderPtr( new log4cxx::ConsoleAppender(layoutPtr, "System.err")); 
   log4cxx::BasicConfigurator::configure(appenderPtr);
Thanks
Deepak

On Wed, Oct 14, 2009 at 8:41 AM, Zhou Tao <zhoutao109@...> wrote:

Experts,

I am using the log4cxx-0.10.0. And at the begining of the application, I create the log4cxx instances including Logger, FileAppender, PatternLayout etc. Sometime within the application, I need to destroy the instances.

For example,

To create the below objects at the begining,

_layout = new log4cxx::PatternLayout(format);

_fileAppender = new log4cxx::RollingFileAppender();

....

Then somewhere to remove the above objects like the below,

delete _fileAppender;

delete _layout;

....

However when deleting the objects, always core dump on windows. On unix, when the application exit, also get a core dump.

Then how to clean up the log4cxx instances or a sequence is required when deleting the objects? or some example code?

Any suggestion are highly appreciated.

Thanks,

Tom

Re: How to clean up the log4cxx objects to avoid the memory leak?

2009-10-13T22:20:22Z

You should use smart pointer instead.
e.g

    log4cxx::LogManager::resetConfiguration(); 
   log4cxx::LayoutPtr layoutPtr(new log4cxx::PatternLayout("%c-%p (%d{dd MMM yyyy HH:mm:ss}) [%-5t] %m%n")); 

   log4cxx::AppenderPtr appenderPtr( new log4cxx::ConsoleAppender(layoutPtr, "System.err")); 
   log4cxx::BasicConfigurator::configure(appenderPtr);

Thanks
Deepak

On Wed, Oct 14, 2009 at 8:41 AM, Zhou Tao <zhoutao109@...> wrote:

Experts,

I am using the log4cxx-0.10.0. And at the begining of the application, I create the log4cxx instances including Logger, FileAppender, PatternLayout etc. Sometime within the application, I need to destroy the instances.

For example,

To create the below objects at the begining,

_layout = new log4cxx::PatternLayout(format);

_fileAppender = new log4cxx::RollingFileAppender();

....

Then somewhere to remove the above objects like the below,

delete _fileAppender;

delete _layout;

....

However when deleting the objects, always core dump on windows. On unix, when the application exit, also get a core dump.

Then how to clean up the log4cxx instances or a sequence is required when deleting the objects? or some example code?

Any suggestion are highly appreciated.

Thanks,

Tom

How to clean up the log4cxx objects to avoid the memory leak?

2009-10-13T20:11:45Z

Experts,

I am using the log4cxx-0.10.0. And at the begining of the application, I create the log4cxx instances including Logger, FileAppender, PatternLayout etc. Sometime within the application, I need to destroy the instances.

For example,

To create the below objects at the begining,

_layout = new log4cxx::PatternLayout(format);

_fileAppender = new log4cxx::RollingFileAppender();

....

Then somewhere to remove the above objects like the below,

delete _fileAppender;

delete _layout;

....

However when deleting the objects, always core dump on windows. On unix, when the application exit, also get a core dump.

Then how to clean up the log4cxx instances or a sequence is required when deleting the objects? or some example code?

Any suggestion are highly appreciated.

Thanks,

Tom

Build fail on AIX using XLC compiler

2009-09-29T18:36:22Z

Hi all,

I am building log4cxx on AIX using XLC as the compiler. And I turn on the -D_LARGE_FILES compiler flag for our purpose. However seems that log4cxx dislikes the compiler flag. I could build APR, APR-UTIL and when I build log4cxx, errors happen when build the simpledateformat.cpp file. The error message is the following,

/bin/sh ../../../libtool --tag=CXX --mode=compile /usr/vacpp/bin/xlC_r -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"log4cxx\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_MBSRTOWCS=1 -DHAVE_WCSTOMBS=1 -DHAVE_SYSLOG=1 -DHAVE_FWIDE=1 -I. -I. -I../../../src/main/include -I../../../src/main/include -I/usr/vacpp/include -U__STR__ -D_THREAD_SAFE -D_USE_IRS -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr/include/apr-1 -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr-util/include/apr-1 -q64 -D_LARGE_FILES -qlonglong -c -o simpledateformat.lo simpledateformat.cpp
/usr/vacpp/bin/xlC_r -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"log4cxx\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_MBSRTOWCS=1 -DHAVE_WCSTOMBS=1 -DHAVE_SYSLOG=1 -DHAVE_FWIDE=1 -I. -I. -I../../../src/main/include -I../../../src/main/include -I/usr/vacpp/include -U__STR__ -D_THREAD_SAFE -D_USE_IRS -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr/include/apr-1 -I/usr/u/tzhou/log4cxx_build/aixibmp64/nodebug/install/apr-util/include/apr-1 -q64 -D_LARGE_FILES -qlonglong -c -M simpledateformat.cpp -DPIC -o .libs/simpledateformat.o
"simpledateformat.cpp", line 735.15: 1540-1118 (S) The declaration of "defaultLocale" uses the undefined class "std::locale" when the class must be complete.
"simpledateformat.cpp", line 124.25: 1540-0218 (S) The call does not match any parameter list for "std::has_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >".
"/usr/vacpp/include/locale", line 194.14: 1540-1283 (I) "std::_LFS_ON::has_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 124.35: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
"simpledateformat.cpp", line 125.63: 1540-0218 (S) The call does not match any parameter list for "std::use_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >".
"/usr/vacpp/include/xlocale", line 293.19: 1540-1283 (I) "std::_LFS_ON::use_facet<std::_LFS_ON::time_put<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 125.73: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
"simpledateformat.cpp", line 136.25: 1540-0218 (S) The call does not match any parameter list for "std::has_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >".
"/usr/vacpp/include/locale", line 194.14: 1540-1283 (I) "std::_LFS_ON::has_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 136.35: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
"simpledateformat.cpp", line 137.60: 1540-0218 (S) The call does not match any parameter list for "std::use_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >".
"/usr/vacpp/include/xlocale", line 293.19: 1540-1283 (I) "std::_LFS_ON::use_facet<std::_LFS_ON::time_put<char,std::ostreambuf_iterator<char,std::char_traits<char> > > >(const locale &)" is not a viable candidate.
"simpledateformat.cpp", line 137.70: 1540-0256 (I) A parameter of type "const std::_LFS_ON::locale &" cannot be initialized with an expression of type "const std::locale".
make[3]: *** [simpledateformat.lo] Error 1

Any insight for this issue is greatly appreciated.
Tom

RE: log4cxx with JNI... Crashes when using appender and layout?

2009-09-25T06:33:26Z

log4cxx with JNI... Crashes when using appender and layout?

Fixed.

Was a problem with the built libraries I was using.

I simply rebuilt the project and now work!

Matt Zmuda

Software Developer - Tools Group

From: Zmuda, Matthew [mailto:Matthew_Zmuda@...]
Sent: September 25, 2009 8:20 AM
To: Log4CXX User
Subject: RE: log4cxx with JNI... Crashes when using appender and layout?

I wanted to add to this issue.

I noticed the error only occurs once the app finishes running, so probably when the DLL is unloading and there is some cleaning occurring.

Should I be doing any cleanup from the below code? I didn’t look into it much yet but it seems that all the XxxxxPtr classes are smart pointers?

And from examples I’ve seen there has been no cleanup.

Thanks,

Matt Zmuda

Software Developer - Tools Group

From: Zmuda, Matthew [mailto:Matthew_Zmuda@...]
Sent: September 24, 2009 5:38 PM
To: log4cxx-user@...
Subject: log4cxx with JNI... Crashes when using appender and layout?

When calling native code from java the following works when making the native calls:

BasicConfigurator::configure();

LoggerPtr rootLogger = Logger::getRootLogger();

LOG4CXX_DEBUG(rootLogger, "debug message");

LOG4CXX_INFO(rootLogger, "info message");

LOG4CXX_WARN(rootLogger, "warn message");

LOG4CXX_ERROR(rootLogger, "error message");

LOG4CXX_FATAL(rootLogger, "fatal message");

If I try setting appender and layout like:

LoggerPtr rootLogger = Logger::getRootLogger();

log4cxx::ConsoleAppenderPtr appender(new log4cxx::ConsoleAppender());

log4cxx::LayoutPtr layout(new log4cxx::SimpleLayout());

appender->setLayout(layout);

log4cxx::helpers::Pool pool;

appender->activateOptions(pool);

rootLogger->addAppender(appender);

LogManager::getLoggerRepository()->setConfigured(true);

LOG4CXX_DEBUG(rootLogger, "debug message");

LOG4CXX_INFO(rootLogger, "info message");

LOG4CXX_WARN(rootLogger, "warn message");

LOG4CXX_ERROR(rootLogger, "error message");

LOG4CXX_FATAL(rootLogger, "fatal message");

I get memory could not be “written” Application error and JVM crashes. The messages show up in proper format and all but after that what I get.

Any ideas?

Matt Zmuda

Software Developer - Tools Group

TVWorks - Platform Division, London, Canada

(519) 963-4304

RE: Are log4j and log4cxx configuration files identical?

2009-09-25T05:24:27Z

Thanks for this!

Matt Zmuda
Software Developer - Tools Group

-----Original Message-----
From: log4cxx [mailto:log4cxx@...]
Sent: September 25, 2009 8:16 AM
To: Log4CXX User
Subject: Re: Are log4j and log4cxx configuration files identical?

>I am coding a JNI project and planning to use log4j in java portion and log4cxx in c++.
>Can the same configurations files be used for both?
The formats are the same, but because of the answer to your third question, you may need two different files unless you add appenders
programmatically, or split your loggers such that C++ loggers go to one appender and Java loggers go to another.

>If I change logging level at runtime in Java will the changes also be made in c++ logger?
If you are making the changes in Java, they will not have any affect on the log4cxx logging configuration. If you are making changes to the file, and
you have both your Java initialization and C++ initialization both set up to configure and watch, then both should see the file change and reconfigure
based on the new file settings.

>Finally can both Java and C++ loggers log to the same file?
Both Java and C++ will try to open the file with write permissions, so this will not work.

-Andy

RE: log4cxx with JNI... Crashes when using appender and layout?

2009-09-25T05:20:00Z

log4cxx with JNI... Crashes when using appender and layout?

I wanted to add to this issue.

I noticed the error only occurs once the app finishes running, so probably when the DLL is unloading and there is some cleaning occurring.

Should I be doing any cleanup from the below code? I didn’t look into it much yet but it seems that all the XxxxxPtr classes are smart pointers?

And from examples I’ve seen there has been no cleanup.

Thanks,

Matt Zmuda

Software Developer - Tools Group

From: Zmuda, Matthew [mailto:Matthew_Zmuda@...]
Sent: September 24, 2009 5:38 PM
To: log4cxx-user@...
Subject: log4cxx with JNI... Crashes when using appender and layout?

When calling native code from java the following works when making the native calls:

BasicConfigurator::configure();

LoggerPtr rootLogger = Logger::getRootLogger();

LOG4CXX_DEBUG(rootLogger, "debug message");

LOG4CXX_INFO(rootLogger, "info message");

LOG4CXX_WARN(rootLogger, "warn message");

LOG4CXX_ERROR(rootLogger, "error message");

LOG4CXX_FATAL(rootLogger, "fatal message");

If I try setting appender and layout like:

LoggerPtr rootLogger = Logger::getRootLogger();

log4cxx::ConsoleAppenderPtr appender(new log4cxx::ConsoleAppender());

log4cxx::LayoutPtr layout(new log4cxx::SimpleLayout());

appender->setLayout(layout);

log4cxx::helpers::Pool pool;

appender->activateOptions(pool);

rootLogger->addAppender(appender);

LogManager::getLoggerRepository()->setConfigured(true);

LOG4CXX_DEBUG(rootLogger, "debug message");

LOG4CXX_INFO(rootLogger, "info message");

LOG4CXX_WARN(rootLogger, "warn message");

LOG4CXX_ERROR(rootLogger, "error message");

LOG4CXX_FATAL(rootLogger, "fatal message");

I get memory could not be “written” Application error and JVM crashes. The messages show up in proper format and all but after that what I get.

Any ideas?

Matt Zmuda

Software Developer - Tools Group

TVWorks - Platform Division, London, Canada

(519) 963-4304

Re: Are log4j and log4cxx configuration files identical?

2009-09-25T05:16:02Z

>I am coding a JNI project and planning to use log4j in java portion and log4cxx in c++.
>Can the same configurations files be used for both?
The formats are the same, but because of the answer to your third question, you may need two different files unless you add appenders programmatically, or split your loggers such that C++ loggers go to one appender and Java loggers go to another.

>If I change logging level at runtime in Java will the changes also be made in c++ logger?
If you are making the changes in Java, they will not have any affect on the log4cxx logging configuration. If you are making changes to the file, and you have both your Java initialization and C++ initialization both set up to configure and watch, then both should see the file change and reconfigure based on the new file settings.

>Finally can both Java and C++ loggers log to the same file?
Both Java and C++ will try to open the file with write permissions, so this will not work.

-Andy

log4cxx with JNI... Crashes when using appender and layout?

2009-09-24T14:38:27Z

log4cxx with JNI... Crashes when using appender and layout?

When calling native code from java the following works when making the native calls:

BasicConfigurator::configure();

LoggerPtr rootLogger = Logger::getRootLogger();

LOG4CXX_DEBUG(rootLogger, "debug message");

LOG4CXX_INFO(rootLogger, "info message");

LOG4CXX_WARN(rootLogger, "warn message");

LOG4CXX_ERROR(rootLogger, "error message");

LOG4CXX_FATAL(rootLogger, "fatal message");

If I try setting appender and layout like:

LoggerPtr rootLogger = Logger::getRootLogger();

log4cxx::ConsoleAppenderPtr appender(new log4cxx::ConsoleAppender());

log4cxx::LayoutPtr layout(new log4cxx::SimpleLayout());

appender->setLayout(layout);

log4cxx::helpers::Pool pool;

appender->activateOptions(pool);

rootLogger->addAppender(appender);

LogManager::getLoggerRepository()->setConfigured(true);

LOG4CXX_DEBUG(rootLogger, "debug message");

LOG4CXX_INFO(rootLogger, "info message");

LOG4CXX_WARN(rootLogger, "warn message");

LOG4CXX_ERROR(rootLogger, "error message");

LOG4CXX_FATAL(rootLogger, "fatal message");

I get memory could not be “written” Application error and JVM crashes. The messages show up in proper format and all but after that what I get.

Any ideas?

Matt Zmuda

Software Developer - Tools Group

TVWorks - Platform Division, London, Canada

(519) 963-4304