Ok, I finally finished rebuilding the log4cxx stuff, recompiling this (big)
project, fixing log4cxx, re-recompiling, and finally deploying and running,
and I get a segfault (but not the same IOT/Abort Trap message). I went back
to my simple program, and got the same thing, not even any logging output
now. Here is my test program:
#include <log4cxx/logger.h>
#include <log4cxx/basicconfigurator.h>
using namespace log4cxx;
int main(int argc, char * argv[])
{
LoggerPtr root = Logger::getRootLogger();
BasicConfigurator::configure();
root->debug("foo!");
return 0;
}
Compiled with gcc on AIX 5.3 with flags -g and -maix64, as were log4cxx,
apr, and apr-util. Any suggestions?
Thanks,
Marshall
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Curt Arnold
Sent: 2007-May-23 Wed 5:55 PM
To: Log4CXX User
Subject: Re: IOT/Abort Trap on AIX 5.3
On 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, removed the call to error() from
> Logger::getResourceBundle(), recompiled log4cxx, and everything was
> fine.
> Not sure if this solution is really ideal, but it did work :P
>
>
> Marshall
>
Andreas recently committed changes to make that function const
(http://marc.info/?l=log4cxx-dev&m=117916477809150&w=2 and http://
marc.info/?l=log4cxx-dev&m=117916259518459&w=2) along with other
changes to avoid pedantic warnings from gcc. Looks like the changes
need to be reviewed.
