On May 8, 2005, at 8:57 AM, Chris Williams wrote:
I am trying to compile the cvs head version of log4cxx on Solaris 10.
I
grabed the cvs versions of ant-contrib, cpptask, and log4cxx. I am
using
ant 1.6.3 and gcc 3.4.2. I have attached a sample of the errors I get
from
the cc task. Now when
On May 9, 2005, at 10:04 AM, Javier wrote:
C:\temp\log4cxx\logging-log4cxx>ant -v build-projects-vc6
But I received the following error message:
Apache Ant version 1.6.3 compiled on April 28 2005
This sounds very similar to a problem reported by Paul Nader last week
(http://marc.theaimsgroup.com/?
ch is provided by Ant. Could you try rebuilding cpptasks and
ant-contrib using Ant 1.6.3.
On May 9, 2005, at 10:53 AM, Javier wrote:
On 09/05/2005 at 10:25 Curt Arnold wrote:
On May 9, 2005, at 10:04 AM, Javier wrote:
C:\temp\log4cxx\logging-log4cxx>ant -v build-projects-vc6
But I received the followi
RollingFileAppender is stubbed out in log4cxx at the moment in
anticipation of porting over the log4j 1.3 new Rolling File framework.
Try using a FileAppender. Should have RFA's on-line within the week.
On Jun 29, 2004, at 3:55 AM, Michaël CATANZARITI wrote:
Hello,
In order to send events to Chainsaw, you have to use the
XMLSocketAppender and not the SocketAppender, since the binary formats
are not compatible
I assume the incompatibility was not intentional. Would the project be
open to a
On Jun 30, 2004, at 2:35 PM, Picaso wrote:
Hi,
I would like to know if there's any limitation on the length of string
that
can be logged. I tried the following:
Looking at the include/log4cxx/helpers/tchar.h, it appears that any
message that is converted from ASCII to Unicode or vice-versa is
t
I ran into a few minor gotchas while trying to build log4cxx-0.9.7 on
Mac OS/X. Since nobody else has reported their Mac build experiences,
I thought I pass along mine.
autogen.sh calls libtoolize which is appears to be called glibtoolize
on Mac OS/X.
src/serversocket.cpp needs to include or
log4cxx uses the WIN32 preprocessor macro in several places.
Microsoft Visual C++ and Borland C++ predefine the _WIN32 macro when
building on Win32, but not WIN32 (Visual Studio will explicitly add a
/DWIN32 to the command line by default). I checked the Xerces-C code
base to see how they ha
On Jul 2, 2004, at 9:11 AM, Adnene Ben Abdallah wrote:
Hi,
I had a problem when I tried to build log4cxx with the last MS
Platform
SDK available. I got the following message:
Configuration: dll - Win32
Release
Compiling...
condition.cpp
F:\Development\IPA
Including include/log4cxx/helpers/tchar.h before the Win32 platform's
tchar.h will result in compilation errors as the Win32 tchar.h's
overrides the definitions of W2A, A2W, USES_CONVERSION etc. These
compilation errors can be avoided by forcing the Win32's tchar.h to be
loaded first, but at l
In http://logging.apache.org/log4cxx/manual/Introduction.html, there
are several statements that may mislead developers just starting with
log4cxx (like me), some are obviously hold overs from the short
introduction to log4j. I scanned the entire archive of the
log4cxx-user and log4cxx-dev mai
On Jul 5, 2004, at 1:48 AM, Michaël CATANZARITI wrote:
Hello Curt,
These macros are defined in log4cxx because they don't exist on Unix
platforms.
However I think they should not appear at the log4cxx library
interface, so the conflict will not exist anymore.
It will be fixed in the next version.
Another scenario that seems troubling is when a filename is specified
in an XML configuration file that contains a character not
representable in the current locale code page when using a non-Unicode
version of log4cxx. I assume that the filename would be mangled.
I don't think using UTF-8 int
Attachments to the mailing list are problematic. The more common
practice in other projects is to log a bug and attach the patch to the
bug. Many processes require a bug report for any change to the
project. I haven't seen any mention of it, but there is a log4cxx
entry in Apache's Jira bug-
Thanks for the patch. There have been a couple of emails related to
Unicode support in log4cxx over the past few weeks and I believe that
to do it right will require more changes than just fixing one appender,
however I will review your patch as part of that effort.
Currently, log4cxx has the
On Jul 23, 2004, at 3:25 PM, [EMAIL PROTECTED] wrote:
I have a few questions:
1) Is it possible to make DailyRollingFileAppender delete files older
than
n days (hours, mins,...)? I was looking for something like that in the
code
but was not able to find anything. If it currently is not possible,
On Jul 23, 2004, at 4:41 PM, [EMAIL PROTECTED] wrote:
On Jul 23, 2004, at 3:25 PM, [EMAIL PROTECTED] wrote:
I have a few questions:
1) Is it possible to make DailyRollingFileAppender delete files older
than
n days (hours, mins,...)? I was looking for something like that in
the
As far as I can tel
On Jul 26, 2004, at 6:38 AM, [EMAIL PROTECTED] wrote:
public) from Ceki Gulcu mentioned that DailyRollingFileAppender had
been
deprecated in log4j in preference for RollingFileAppender.
Does this mean that DailyRollingFileApender is going to be removed from
log4cxx ?
I have not been able to find a
On Jul 27, 2004, at 7:29 AM, [EMAIL PROTECTED] wrote:
There are 13 memory leaks and 7 resource leaks reported at the end of
execution. I am still trying to figure out most of them, but here's
where
some of the leaks reported are coming from:
timezone.cpp line 32 [2 leaks - calling tzset and
On Jul 29, 2004, at 12:07 PM, Zendle, Joseph wrote:
Does anyone know the proper way to file a bug for log4cxx?
On Jul 13, 2004, at 12:17 PM, Michaël CATANZARITI wrote:
Hello,
From now on, the log4cxx bug repository is available at
http://nagoya.apache.org/jira/browse/LOGCXX
If you think there are n
On Aug 10, 2004, at 6:11 AM, Danny Pike wrote:
I sent it off but nothing happened, as far as I can see. I don't know
how long it takes for these things to get added. I get the impression
that it is rather too much for the team to handle :)
DP
I've added a bug for this feature request:
http://na
In
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-
[EMAIL PROTECTED]&msgNo=202, troy d.straszheim offered
modifications of the LOG4CXX_DEBUG and similar macros to use
boost::format to construct messages. My take (in the follow up
message) was that the LOG4CXX_DEBUG macros sho
t would be:
#define LOG4CXX_UNLIKELY(x) __builtin_expect(x, 0)
On Aug 12, 2004, at 10:04 AM, Christophe de VIENNE wrote:
Curt Arnold wrote:
Several compilers including gcc have a mechanism to hint that one
branch of an if statement is more likely to be executed. It may be
desirable that the LOG
On Aug 13, 2004, at 9:44 AM, Christophe de VIENNE wrote:
Any idea/suggestion welcome,
Not directly on point, but I had a couple of random, unconsidered
thoughts related to threads that I'd like to throw out if anyone is
going to be digging into to this.
1. Apache Portable Runtime (http://apr.ap
2. The CriticalSection instance in log4cxx::helpers::ObjectImpl
causes config.h to be expanded for the abstract classes in public
API. Isolating implementation details from the client API would
require removing the CriticalSection from the abstract base class and
reintroducing it in the concre
I have an Ant build script that will build log4cxx that I'll check with
the Visual C++ 2003 toolkit and commit. I've used to to build with
Borland C++ builder and to generate CBuilderX and Xcode project files.
On Aug 16, 2004, at 7:15 PM, Barak Simon wrote:
Hi,
Is there a simple way to build th
On Aug 18, 2004, at 1:47 AM, Barak Simon wrote:
Thanks! - seems to work fine for me.
BTW - do you know (or anyone else) by any chance in which windows
library the NT eventlogging methods are defined?
I seem to have the WinBase.h header file with these methods
signatures, but justifiably have li
On Aug 23, 2004, at 3:28 PM, Sean Rohead wrote:
I'm trying to use log4cxx in a win32 Unicode project and am having some
difficulties. If I don't #define UNICODE, the log4cxx::String is a
basic_string (because windows uses _UNICODE). If I do #define
UNICODE, then I get:
There are some pretty serio
On Aug 24, 2004, at 4:52 PM, Michaël CATANZARITI wrote:
Hello,
Can you be more precise and give code samples, please ?
Regards,
Combes, Chris M. wrote:
Folks,
I have an application which configures my logging system through a
ProperyConfigurator. The application instantiates objects which are
imp
On Aug 24, 2004, at 5:15 PM, Sean Rohead wrote:
I am still confused. I am including windows' tchar.h before
log4cxx/logger.h. Here's what windows' tchar.h looks like:
#ifndef _TCHAR_DEFINED
#if !__STDC__
typedef wchar_t TCHAR;
#endif
#define _TCHAR_DEFINED
#endif
Notice how it #defines _T
On Aug 27, 2004, at 3:27 AM, Tom Quarendon wrote:
Right. So to make log4cxx work properly across multiple DLLs with all
my C++
classes having static LoggerPtr objects I need to indulge in some
serious
use of the GCC "init_priority" attribute to control initialisation
order.
Surely there is a rec
On Aug 30, 2004, at 4:45 AM, Barak Simon wrote:
Hi,
1. Could someone please advice me as to what's the best way to add a
flag to PatternLayout?
I need to support Process ID (or is that already supported?), but wish
it to be runtime configurable like any other layout flag.
I thought of two differe
It is a known issue which has been resolved in the CVS version, see
http://nagoya.apache.org/jira/browse/LOGCXX-8.
Basically the signatures for the InterlockedMethods changed in the
Platform SDK sometime between VC6 and VC7. If you are getting this
error, you are most likely using VC6 with a l
I had noticed the potential for the problem and logged it as
http://nagoya.apache.org/jira/browse/LOGCXX-11. Thanks for confirming
that is actually a problem. My suspicion is that gmtime or gmtime_r is
not adequate since log4cxx may need to format times to a time-zone
other than the current t
On Sep 3, 2004, at 3:56 AM, Mattias Brändström wrote:
Hello!
I have two questions about the log4cxx API.
First of all, when I configure log4cxx in the following way:
log4cxx::PropertyConfigurator::configure(string("/usr"));
it fails silently. Is this the way it is supposed to behave? I would
h
On Sep 8, 2004, at 7:38 AM, Robert Haschke wrote:
Dear developers,
I'm new to log4* and I'm wondering how I can achieve the following
goal:
I want to have a top level logger, logging to cerr with a level
WARNING.
Below may be several other loggers with their own appenders, layouts
and
logging l
log4cxx follows log4j and log4j does not attempt to synchronize file
I/O across multiple processes. This is addressed in Chapter 10 of "The
complete manual log4j".
Q 10.3 Can multiple Java Virtual Machines log to the same file using
log4j?
No, there is no way for log4j to coordinate the acces
The intro to log4cxx is misleading in that omits several default
arguments in the prototypes for Logger.debug and similar.
Those methods have arguments for the current source file name and line
number which are provided when the LOG4CXX_ macros are used. The short
answer is to use the macros.
There is a closed bug relating to setting the threshold of an appender,
http://nagoya.apache.org/jira/browse/LOGCXX-12. The bug has been
marked fixed, but within the last month. Are you seeing the behavior
with the CVS version or with 0.9.7?
Thanks for the swift reply.
Legally speaking I do
On Sep 21, 2004, at 8:04 PM, Barak Simon wrote:
Do you know if there are any immediate plans to release a new version?
I don't believe so. I don't think the current state is a good spot for
a release. There are significant unresolved issues (resetting the user
specified time zone and the segmen
Has anybody seen this or have any ideas about how to get around it.?
Try replacing
#include
with
#include
and let the list knows if that fixes the problem. streambuf is a
lower-level include file that is implied in the much more frequently
used sstream include file.
Can some body tell me what difference does the #define macro for
LOG4CXX_DEBUG makes for a shared object to that of
an executable.
sample code...
1)string str1 = "this is devender ";
2)LOG4CXX_DEBUG(loggerx, _T("MSG ") << str1);
3)int i = 0;
4)LOG4CXX_DEBUG(loggerx, _T("MSG ") << i++);
I apprecia
On Oct 13, 2004, at 1:57 AM, Devender Marri wrote:
Hi Curt,
Thank you for the reply, atleast I now know that there is indeed a
problem, as I was trying different ways to solve the problem.
currently I am using std::ostrstream to do the same and found that it
works.
my new code looks as follows
s
On Oct 13, 2004, at 5:45 AM, Sebastian Gurgul wrote:
Hello
My configuration is:
Solaris 8 Intel
gcc 2.95.3
I'm trying to compile log4cxx (0.9.7)...
First I updated/installed: m4, libtool, autoconf, automake
Than I run configure script: ./configure --prefix=$HOME/local
--exec-prefix=$HOME/local
And
On Oct 19, 2004, at 10:24 AM, Conway Allen wrote:
A remark, a problem, a question - I hope they haven't been brought up
before (yes, I've looked)...
1. Exception's getMessage is not declared as const, yet it clearly is.
Thanks, will check.
2. If I write something like...
#include
On Oct 20, 2004, at 5:03 AM, Xiong, Wei (Wei) wrote:
Hello, everybody,
I degrade my automake from 1.9.2 to 1.6.3, and libtool from 1.5.10 to
1.4.3.
This time, I successfully build log4cxx-0.9.7 on Solaris 9 x86.
(Although I
already build one by writing a makefile for it, ^_^.).
But when I build a
Thanks, the traceback is consistent with attempting to configure before
the static string DEBUG_KEY has been constructed. I've just completed
a fairly wide-ranging patch that eliminates use of non-local static
variables (see item 47 in Effective C++ for background) within log4cxx.
However,
Jira is still down, so I went ahead and committed a patch that
eliminates dependency on all non-local static variables (didn't mess
with ThreadLocalStorage). I would appreciate any feedback especially
from those who reported segmentation faults at startup.
On Oct 20, 2004, at 7:24 PM,
This had been reported as bug LOGCXX-17
(http://nagoya.apache.org/jira/browse/LOGCXX-17). There are several
date and time related issues that I should be reviewed as a group, but
I haven't gotten there yet.
On Oct 22, 2004, at 3:11 AM, Barak Simon wrote:
Hi,
It seems Timezone is not thread-saf
I waited hoping someone else would answer this. I don't know. There
is no work ongoing or planned on SocketHubAppender other than a wish
that the serialized format used by SocketAppender and SocketHubAppender
were compatible with log4j
(http://nagoya.apache.org/jira/browse/LOGCXX-7). There a
I've started a discussion on the log4cxx-dev mailing list on the use of
APR and/or ICU4C. Any comments are appreciated (but on the log4cxx-dev
mailing list)
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-
[EMAIL PROTECTED]&msgNo=331
Both the missing sys/types.h include and the static initialization have
been fixed in the CVS version. The Ant build file is able to generate
XCode project files (along with CBuilderX and MSVC projects), though
there are some minor issues with the define and include paths that I
need to fix i
The project file support is only in the CVS version of cpptasks. I
need to get a release done there too. Commenting out the project
should only suppress the project file generation. I haven't seen the
compiler errors, but I'll double check that I haven't committed a
conflict marker or simila
On Nov 4, 2004, at 7:46 AM, Kay Eckernkamp wrote:
Hi,
I am trying to include log4cxx 0.9.7 into my projects and I am
running into several problems.
1st problem occurs if I try to compile the log4cxx.dll in msdev6.0.
The following error occurs:
condition.cpp
C:\kay\log4cxx-0.9.7\src\con
On Nov 5, 2004, at 7:23 AM, Madan, Hatinder wrote:
Hello everybody,
I have compiled the log4cxx and built the shared library on Solaris 8
platform.
While I link this library dynamically to build my executable, I see
the following error:
1) How is the scope for the undefined symbols being resolv
The types of problems you are reporting suggest that you are using a
Unicode configuration to build the app. If you don't need it right at
the moment, I would suggest sticking with a non-Unicode build until the
0.9.8 is available.
The current approach used to handle Unicode within log4cxx is f
Michael has notified the Logging Project Management Committee and the log4cxx
committers that he does not expect to be involved in the project again until
November 2005. Though we will miss Michael his absence does not indicate that
the project is dead. log4cxx is still being actively (maybe t
me resources, but a lot of the time, I have developers who aren't fully utilized. Though we're getting packed lately, maybe we can help with something?
Renny Koshy
President & CEO
RUBIX Information Technologies, Inc.
www.rubixinfotech.com
DailyRollingFileAppender has been deprecated in log4j for quite a
while. The 0.9.7 implementation has problems and I have removed it
from the CVS and will not appear in 0.9.8. The recommended replacement
is RollingFileAppender with a time-based strategy, however I have not
confirmed that log4
On Nov 24, 2004, at 4:24 PM, Malcolm Melville wrote:
It appears to me that there is a memory leak from tchar.h under
Windows in DLL mode. Each construct/destruct cycle of a StringBuffer
causes a 4 byte leak to be reported by Purify and Leak Browser.
The following code fragment - a stripped out v
On Nov 25, 2004, at 1:16 AM, Anton Müller wrote:
Hi,
I wanted to use Log4j Chainsaw v2 and write
to a socket with log4cxx 0.97 but I didnt get it
to work.
Before I continue to check this I have some small questions:
- Is "Log4j Chainsaw v2" usable with log4cxx or are there
binary incompabilities
Cross language operation *never* worked with Java serialization, did
it? It's not a new problem, is it?
I wonder how difficult it would be to *efficiently* transmit
LoggingEvents over the wire, possibly in language neutral way.
Java's Object Serialization Stream Protocol is publicly available
(htt
A logger is should be thread-safe and can be used from multiple
threads. You do not need to request a logger for each thread. If you
do, you will just get multiple references to the same logger object.
The things you cannot do (without using socket listener) is to write
have two appenders wri
You may need to remove any "namespace log4cxx" and use
"log4cxx::LoggerPtr" to declare your logger reference. By removing the
"namespace log4cxx", you will eliminate the ambiguity between
log4cxx::ostream and std::ostream.
On Dec 6, 2004, at 11:45 AM, Jeff Lynn wrote:
Hi,
Can someone help me
On Dec 6, 2004, at 10:01 AM, Ulf Renman wrote:
Hi Mike
Could you be a little more elaborate aboute the solution please. I
think
I have the exact problem you describe here but I do not understand how
to
solve it. Im using log4cxx-0.9.7 under linux with g++ 3.2.3. I've
built two
modules as shared
On Dec 6, 2004, at 12:09 PM, Conway Allen wrote:
Writing std::ostream should do the trick (don't ask my why...!)
The error appeared to be in a system header (ios.h), better to remove
the log4cxx namespace from the imported namespaces (or at least import
it after including ios.h) than to tweak a s
Was this related to MinGW thread? I didn't appear to be so I've
changed the subject.
First, let me warn you that there are major changes forthcoming in the
CVS that will significantly impact appenders. I hope to have those
committed in the CVS within the week.
Without more details on the nat
On Dec 6, 2004, at 12:38 PM, Jeff Lynn wrote:
So by not requesting another instance of logger, do you mean I should
use global variable in the main thread dnd and "extern" in worker
threads?
Are you sure you meant threads? Sounds like you might be intended to
talk about child processes which i
On Dec 6, 2004, at 9:28 PM, Jeff Lynn wrote:
Hi,
I am using ConsoleAppender and FileAppender and is looking to learn
about how to use SocketAppender. Are there any write-up or example
code for the SocketAppender "server?" to receive the log message?
What is the template for this SocketAppend
On Dec 7, 2004, at 6:20 AM, Prosenjit Sinha wrote:
Thanx Curt,
The appender class which I am going to create will only be used for
obtaining the logging string from the OStream *os variable(I have
found out
only this mechanism by which I can get the logging string in my own
classis there any o
I am in the process of making some major modifications to log4cxx which
I hope to get the initial commit in a few days. When reviewing
RollingFileAppender, it does appear that it will have to be almost
rewritten. I've stubbed it out in my working copy at the moment.
What is troubling is that
On Dec 8, 2004, at 10:12 PM, Barak Simon wrote:
Hi,
I need to extend LoggingEvent to set some extra information in it,
but it seems that despite being stated in its doco:
"This class is of concern to those wishing to extend log4cxx",
the destructor is not virtual!
I know that extending it and insta
On Dec 9, 2004, at 1:10 AM, Barak Simon wrote:
Hi again,
I have just noticed that the LoggingEvent class contains a
'properties' map,
and provides getter and setter for it.
From a quick look at the log4j code, LoggingEvent's properties seem to
be the combination of the MDC properties and the Log
On Dec 9, 2004, at 7:53 PM, Barak Simon wrote:
Because I need the information (an event-id) to be on a
*logging-message* level,
not a thread or global.
Using MDC (if at all possible) for pushing a per-message id (those ids
are kept in an internal configuration file and are mapped to
a level an
On Dec 9, 2004, at 4:16 PM, [EMAIL PROTECTED] wrote:
I am developing a cross platform system using Log4Cxx, CppUnit, Boost
and STLPort. Under Linux I'm using Gcc 3.3.4 and under Windows VC7.1.
Under Windows it all works pretty well, after some sleepless nights,
but under Linux, Log4Cxx can't find
I've just committed a fairly hefty modification to CVS that represents
the current state of the long pending "Unicode" rework (bug LOGCXX-10).
At present, though it compiles on Linux using the Ant script, I
believe that it is effectively non-functional. Usually, I wait until
all the unit test
On Dec 13, 2004, at 11:12 PM, Prosenjit Sinha wrote:
Thanx Curt,
I have included and it worked.Currently I
am facing a new problem.I was trying to access Ostream *os variable to
get
the logging string.But I failed to get the string.I have explicitely
set the
immediateFlush variable as FALSE.
A
I'm still not convinced that you need anything that can't be done as
effectively by custom appenders or layouts. It may or may not be more
efficient to take the approach that you have picked, however I know it
will be more likely to break as log4cxx evolves. At this point, I
think you are int
On Dec 13, 2004, at 9:29 AM, Sluis, Minto van der wrote:
Hi all,
Does anyone know if or when the SocketAppender (and other socket
related code) gets converted to APR?
Will this change be in the next release?
When is the next release scheduled?
I could give a hand if my employer it.
SocketApp
Chainsaw and log4cxx's XMLSocketAppender work together so I've heard.
log4cxx's SocketAppender has used an incompatible wire format which is
not compatible with log4j's logging event serialization. There has
been a long outstanding bug to make the wire formats compatible but no
effort has bee
On Dec 14, 2004, at 3:04 AM, Prosenjit Sinha wrote:
Hi,
Can anybody tell me if there is any book on log4cxx.There is a book on
log4j
called "Complete Manual log4j".Is there anything similar to that for
log4cxx
Cheers
Prosenjit
No, I don't believe that there is. I think the goal is to keep log4c
On Dec 13, 2004, at 9:03 AM, Sluis, Minto van der wrote:
Hi,
I tried to compile log4cxx for for tru64 using the compaq compiler.
Unfortunately I ran into a lot of compiler errors. Below is a script
to resolve a few of the errors. This script strips the trailing semi-
colon from namespace declara
I've added some unit tests for the new classes, updated the GNU make
build and the example files. I'm still getting a segmentation fault
running the unit tests (haven't tracked down which one yet) and haven't
tracked down the linking problem on Windows, but the very simple
example files seem t
On Dec 17, 2004, at 1:10 AM, Manish Moorjani wrote:
Hi All,
A have a ear, which consist of two components backend and frontend
Package structure is like
Abc.bcd.frontend.*
Abc.bcd.backend.*
I want to log the details of the packages in different log files(using
apache's log4j), can anyone help me
On Dec 17, 2004, at 10:59 AM, Ben Arnold wrote:
Hi,
I have a (hopefully) simple question about getting context information
into
my logging.
Say I have a class Agent:
class Agent {
public:
long id() const { return myId_; }
void doSomething();
private:
static LoggerPtr agentLogger_;
};
This a
On Dec 17, 2004, at 10:03 AM, mgr Jan Obdrzalek wrote:
On the page
http://logging.apache.org/log4cxx/manual/
Introduction.html#DefaultInitializationProcedure
is written some algorithm. I tryed to find implementation of it, but
failed.
Is this algorithm implemented somewhere or am I supposed to
Some of the more cryptic comments were copied over from log4j and may
or may not apply to log4j If the same comments appear in the log4j
source you might search the log4j mailing lists and ask there. There
is definitely a more continuous history there. I personally can't tell
you what happe
You may find some answers if you check the archives. Cygwin wasn't a
supported platform in 0.9.7 and the current CVS is substantially
different that 0.9.7, so it doesn't benefit the project to try to
resolve issues with that snapshot. The current CVS is recovering from
some major surgery
On Dec 20, 2004, at 6:04 PM, Pedro Ribeiro wrote:
Is there any way to build it using VC7 ?
log4cxx 0.9.7 has Visual Studio 6 project files that are likely to work
with VC7. If not, all I can say is wait for the CVS code base to
stabilize again.
The current CVS contains an Ant build script (usin
On Dec 21, 2004, at 6:35 AM, [EMAIL PROTECTED] wrote:
Hi,
I'm writing a custom appender for log4cxx, and have a few questions
about the Object/ObjectImpl/ObjectPtrT classes.Basically I'm going
to code a number of classes that extend ObjectImpl, to make use of the
ObjectPtrT "smart pointer" t
On Dec 21, 2004, at 8:38 AM, [EMAIL PROTECTED] wrote:
Hi Curt,
Good stuff. It looked like hard work using all those macros anyway.
:-) I'll follow your lead and investigate using APR myself for
handling threading issues.
One last thingsorry if this has been asked recently already - I
couldn
On Dec 21, 2004, at 3:28 PM, Barak Simon wrote:
I am actually using both downcast and "invalid casts" checks (which
returns NULL in the cast method) for my log4cxx-derived stuff
(e.g. my DBLogger customised class)
This enables me to detect whether a logger was created as a
log4cxx::Logger or by u
I added your comment to the existing LOGCXX-7 bug on the socket format
being incompatible with Chainsaw
(http://nagoya.apache.org/jira/browse/LOGCXX-7).
On Dec 22, 2004, at 6:04 AM, Sluis, Minto van der wrote:
Hi,
After a little bit of struggling we succeeded in building
0.9.7 on the tru64 using
There was a recent discussion on SocketAppender in log4j and log4net on
the log4j-dev mailing list:
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4j-
[EMAIL PROTECTED]&msgNo=8240. One of the suggestions in that
thread is that binary compatibility based on the existing log4j
seriali
On Dec 23, 2004, at 3:52 AM, Madan, Hatinder wrote:
Hi,
I would like to truncate a field that exceeds its maximum length,
from the end.
But this is what the documentation of log4cxx says:
If the data item is longer than the maximum field, then the extra
characters are removed from the beginning
It is not a facility that I have used, but it is tested in the unit
tests by tests/src/customlogger/xloggertestcase.cpp.
I compared your config file with the tests/input/xml/customLogger1.xml,
the config file for that test and didn't see any significant
differences.
I believe the more likely pr
log4cxx currently contains a method and several macros offering message
construction using resource bundles to support internationalization of
logging messages. Based on a quick review, it appears that these
methods do not correspond to features in log4j or log4net and have no
unit tests assoc
On Jan 4, 2005, at 6:29 PM, Justin Chen wrote:
Hello,
I got a similar problem as the one from Bob Young. The difference is
that when I use logging in a standalone EXE, it works just fine; the
problem occurs when I use it in a DLL called by an EXE. When the EXE
terminates, an error message appear
On Jan 9, 2005, at 11:03 AM, [EMAIL PROTECTED] wrote:
Hi,
Sorry about the subject but that in fact is my question. Is it
recommended to use log4cxx in c++ app for windows? I mean a basic test
revealed a memory leak of 4 bytes every time you log (stack trace from
purify is attached below and I am
The implementation of WriterAppender is radically different in the CVS
and an appender written as you described will not be compatible with
the next development snapshot (the long awaited 0.9.8)
Unless you have a compelling reason to stay with 0.9.7, I would
strongly suggest that you write your
1 - 100 of 652 matches
Mail list logo
