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
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
I may have an afternoon free this weekend and see if I can't regain my train of
thought.
There has been a tension between wanting to avoid memory leaks on shutdown to
not offend Valgrind, Purify et al and not shutting down APR while it is still
being used. There were many previous discussio
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
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
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
Use apr, apr-util, expat, log4cxx libraries compiled with -fPIC flag.
It works in my case.
On Thu, Jul 30, 2009 at 9:06 AM, Curt Arnold wrote:
>
> On Jul 16, 2009, at 7:43 AM, abgimeno wrote:
>
>
>> Hi
>>
>> I have the same problem and I could not solve. I have installed the
>> version
>> apach
On Jul 16, 2009, at 7:43 AM, abgimeno wrote:
Hi
I have the same problem and I could not solve. I have installed the
version
apache-log4cxx-0.10.0. apr-1.3.6 and apr-util-1.3.8. in a Red Hat 5
x64
I tried with the patch 596934 and does not work.
When the program ends gives an exception
Hi
I have the same problem and I could not solve. I have installed the version
apache-log4cxx-0.10.0. apr-1.3.6 and apr-util-1.3.8. in a Red Hat 5 x64
I tried with the patch 596934 and does not work.
When the program ends gives an exception
terminate called after throwing an instance of
'
Hi
I have the same problem and I could not solve. I have installed the version
apache-log4cxx-0.10.0. apr-1.3.6 and apr-util-1.3.8. in a Red Hat 5 x64
I tried with the patch 596934 and does not work.
When the program ends gives an exception
terminate called after throwing an instance of
On Jan 16, 2009, at 11:47 AM, Rhosyn wrote:
The attach patch fixes a thread safety issue we found with
ObjectPtrBase
when we ported our application to a 64 bit platform.
It will only work if you are using a version of apr with
apr_atomic_xchgptr()
Cheers
apr_atomic_xchgptr was added at
11 matches
Mail list logo
