t: 2007-Jun-29 Fri 4:35 PM
To: Log4CXX User
Subject: Re: AIX segfault
On Jun 29, 2007, at 10:31 AM, Marshall Powers wrote:
>
> I did some research and it looks like ISO8859-1 is another name for
> some
> standard US English encoding. I don't know if this "en_US" is
I noticed that the program was crashing in iconv_open("UTF-8", "ISO8859-1").
Out of curiosity, I tried calling that function from my own program, before
"new RollingFileAppender()", to see if it was purely a problem with my IBM
iconv. The segfault vanished. Here is a revised program:
_main.cpp_
#
ipsub : SUCCESS
testlock: SUCCESS
testlfs : SUCCESS
testmmap: SUCCESS
testnames : SUCCESS
testoc : SUCCESS
testpath: SUCCESS
testpipe: SUCCESS
testpoll : |
At this point, testpoll hangs. Any advice for how to remove that group of
unit tests perhaps, so we can find one that exposes this bug?
"4) Would appreciate you keeping the list advised of this one."
Done!
Thanks,
Marshall Powers
I'm getting a segfault on 64-bit AIX 5.3. I'm using static libraries of
log4cxx, apr, and aprutil. Here is a test program and Makefile I am using
that causes the crash:
_main.cpp_
#include
#include
#include
using namespace log4cxx;
using namespace log4cxx::rolling;
int main(in
setEncoder();
} else if (StringHelper::equalsIgnoreCase(charset, "UTF-16LE",
"utf-16le")) {
return new UTF16LECharsetEncoder();
}
#if defined(_WIN32)
throw IllegalArgumentException(charset);
#else
return new APRCharsetEncoder(charset.c_str());
#endif
}
some app that uses APR, and
my user doesn't have "ISO-8859-1" in their iconv, is my app going to crash?)
Thanks,
Marshall Powers
rsion of iconv or with
log4cxx.
Marhall
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Curt Arnold
Sent: 2007-May-24 Thu 11:18 AM
To: Log4CXX User
Subject: Re: IOT/Abort Trap on AIX 5.3
On May 24, 2007, at 9:20 AM, Marshall Powers wrote:
&
May 23, 2007, at 4:00 PM, Marshall Powers wrote:
> OK I solved my own problem.
>
> I looked a little closer, and the only thing that stood out about the
> one-argument error functions was that they were declared const. I
> removed
> the "const" from those two functions,
g4cxx, and everything was fine.
Not sure if this solution is really ideal, but it did work :P
Marshall
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Marshall Powers
Sent: 2007-May-23 Wed 4:41 PM
To: 'Log4CXX User'
Subject: RE: IOT/Abort
te your code snapshot and see if that fixed
your problem.
On May 23, 2007, at 9:26 AM, Marshall Powers wrote:
> I'm getting a runtime error on AIX, "IOT/Abort Trap (core dumped)".
> I wrote
> a small test program to test the log4cxx functionality, compiling
> it wit
ate
the INSTALL file :)
Marshall
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Curt Arnold
Sent: 2007-May-23 Wed 11:18 AM
To: Log4CXX User
Subject: Re: build failed on solaris 9
On May 23, 2007, at 9:59 AM, Marshall Powers wrote:
> I'm not
ned 1 exit status
BUILD FAILED
/export/home/aaggarwal/logging-log4cxx/build.xml:731: gcc failed with
return code 1
anything on this.
thanks
Marshall Powers wrote:
> This is because you need to set compiler flag -D_POSIX_PTHREAD_SEMANTICS.
> The configure script for APR knows this, but th
I'm getting a runtime error on AIX, "IOT/Abort Trap (core dumped)". I wrote
a small test program to test the log4cxx functionality, compiling it with
the same compile options as my larger program. I was able to get some
logging output out of the smaller program, but it crashed with the same
message
This is because you need to set compiler flag -D_POSIX_PTHREAD_SEMANTICS.
The configure script for APR knows this, but the ant build file does not get
the info after running ./configure for APR. Try adding a to the tasks in apr-build.xml.
-Original Message-
From: [EMAIL PROTECTED]
[mailt
o: Log4CXX User
Subject: Re: rollingfileappender ... not rolling?
On Apr 17, 2007, at 11:15 AM, Marshall Powers wrote:
I tried running the unit tests, as you suggested, and they appeared to work
fine. For kicks, I tried reducing the max file size of my
SizeBasedTriggeringPolicy to 100 by
]
[mailto:[EMAIL PROTECTED]
On Behalf Of Curt Arnold
Sent: 2007-Apr-17 Tue 11:52 AM
To: Log4CXX User
Subject: Re: rollingfileappender ... not rolling?
On Apr 17, 2007, at 9:42 AM, Marshall Powers wrote:
This is not a multiple-process situation. It is multi-threaded, but the
logging is
the repository would make things better.
Thanks,
Marshall
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Curt Arnold
Sent: 2007-Apr-17 Tue 1:46 AM
To: Log4CXX User
Subject: Re: rollingfileappender ... not rolling?
On Apr 16, 2007, at 1:01 PM, Marshall
User
Subject: Re: rollingfileappender ... not rolling?
On Apr 16, 2007, at 12:12 PM, Marshall Powers wrote:
I'm trying to use a RollingFileAppender, but my log files are not "rolling"
when it seems that they should. I am using a SizeBasedTriggeringPolicy with
max file
I'm trying to use a RollingFileAppender, but my log files are not "rolling"
when it seems that they should. I am using a SizeBasedTriggeringPolicy with
max file size = 100kb, and a FixedWindowRollingPolicy. When I start my
program, if a log file already exists that is larger than the max file size,
The Log4Cxx docs says that the %l (for location) option in PatternLayout is
"Extremely Slow". Is this true, or was this just something left over from
the Log4j documentation? The two documents are almost identical.
Thanks
Marshall Powers
20 matches
Mail list logo
