deepak singh-4 wrote:
>
> Use apr, apr-util, expat, log4cxx libraries compiled with -fPIC flag.
> It works in my case.
>> I'l try to fire up a copy of CentOS 5 x64 this weekend.
>>
>> Did it occur during the unit tests or one of the sample applications, or
>> in
>> some other context?
>>
>
I
Let me retract that message above the patch and with the option, did not
fix it.
First time running the application, it did this:
terminate called after throwing an instance of
'log4cxx::helpers::MutexException'
what(): Mutex exception: stat = 22
Aborted
Then rerunning it again with th
BTW here is also the stack when one of the exceptions mentioned above is
thrown:
terminate called after throwing an instance of
'log4cxx::helpers::MutexException'
what(): Mutex exception: stat = 1
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x41401940 (LWP 18319)]
0x003
Curt Arnold-3 wrote:
>
> Any specific instructions on reproducing the problem would be appreciated.
> Especially along the lines of
>
> 1. fire up this AMI on Amazon Web Services
> 2. Do this and that
> 3. Crash
>
> Setting up non-default development platforms is a chore and having a
> repro
Hi Curt,
I was reading your
http://www.opensubscriber.com/message/log4cxx-u...@logging.apache.org/4931122.html
post here and I think I understand what I might have done wrong to make it
non-threadsafe (I too had made my logstream a data member). So here's the
modification of my code (though it
