Segmentation fault log4cxx 0.10.0 on app exit ( RH Linux)

Segmentation fault on app exit.

log4cxx, apr-1.2.12 and apr-util-1.2.12 had been build from
tar file.

gcc -v
Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared
--enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk
--host=i386-redhat-linux
Thread model: posix
gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)

$ uname -a
Linux gredhat4 2.6.9-11.EL #1 Fri May 20 18:17:57 EDT 2005
i686 i686 i386
GNU/Linux


Test app successfully writes one line in log file with
code:
int main() {
   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
    LoggerPtr LogManager::cplusLoggerPtr =
Logger::getLogger("API");
    LOG4CXX_INFO(cplusLoggerPtr , "test_info");
    return 0;
}


C++ [C/C++ Local Application]	
	gdb/mi (5/29/08 2:31 PM) (Suspended)	
		Thread [1] (Suspended: Signal 'SIGSEGV' received.
Description:
Segmentation fault.)	
			8 apr_atomic_dec32() atomic/unix/apr_atomic.c:310
0xb7d1efba	
			7 log4cxx::helpers::ObjectImpl::releaseRef()
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp:44
0xb7e36da0	
			6 log4cxx::Logger::releaseRef()
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
0xb7e20c5d	
			5 ~ObjectPtrT()
/usr/local/include/log4cxx/helpers/objectptr.h:100
0x080550e3	
			4 __tcf_1() /home/..project specific...	
			3 exit()  0x004ce467	
			2 __libc_start_main()  0x004b8e2d	
			1 _start()  0x080545ad

Any suggestion is welcome...

Thanks,
Gregory	

-- 
View this message in context: http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17543738.html
Sent from the Log4cxx - Users mailing list archive at
Nabble.com.

Do you have any of the network appenders or possibly the
AsyncAppender
configured? I'm guessing this is the same thread shutdown
issues I
reported on Windows in this thread:

http://www.nabble.com/A-few-problems-to-report-to1
7013024.html

The tip should be a bit better, but you might get a delay on
shutdown.

On Thu, May 29, 2008 at 3:15 PM, GregN <grshoreyahoo.com> wrote:
>
> Segmentation fault on app exit.
>
> log4cxx, apr-1.2.12 and apr-util-1.2.12 had been build
from tar file.
>
> gcc -v
> Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
> Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared
--enable-threads=posix
> --disable-checking --with-system-zlib
--enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-java-awt=gtk
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)
>
> $ uname -a
> Linux gredhat4 2.6.9-11.EL #1 Fri May 20 18:17:57 EDT
2005 i686 i686 i386
> GNU/Linux
>
>
> Test app successfully writes one line in log file with
code:
> int main() {
>   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
>    LoggerPtr LogManager::cplusLoggerPtr =
Logger::getLogger("API");
>    LOG4CXX_INFO(cplusLoggerPtr ,
"test_info");
>    return 0;
> }
>
>
> C++ [C/C++ Local Application]
>        gdb/mi (5/29/08 2:31 PM) (Suspended)
>                Thread [1] (Suspended: Signal 'SIGSEGV'
received. Description:
> Segmentation fault.)
>                        8 apr_atomic_dec32()
atomic/unix/apr_atomic.c:310 0xb7d1efba
>                        7
log4cxx::helpers::ObjectImpl::releaseRef()
>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp:44
> 0xb7e36da0
>                        6 log4cxx::Logger::releaseRef()
>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
> 0xb7e20c5d
>                        5 ~ObjectPtrT()
/usr/local/include/log4cxx/helpers/objectptr.h:100
> 0x080550e3
>                        4 __tcf_1() /home/..project
specific...
>                        3 exit()  0x004ce467
>                        2 __libc_start_main() 
0x004b8e2d
>                        1 _start()  0x080545ad
>
> Any suggestion is welcome...
>
> Thanks,
> Gregory
>
> --
> View this message in context: http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17543738.html
> Sent from the Log4cxx - Users mailing list archive at
Nabble.com.
>
>



-- 
Dale King

I am facing similar issue with Solaris. 
The following link explains my issue.

http://mail-archives.apache.org/mod_mbox
/logging-log4cxx-user/200804.mbo
x/%3cEB4C465FC146B54DAADF4C8C0637BC6202BA6C6DHQ-EXCH-4.corp.brocade.com
%3e

Couldn't really get out of this yet.

Regards
Unni
-----Original Message-----
From: Dale King [mailto:dalewkinggmail.com] 
Sent: Thursday, May 29, 2008 2:06 PM
To: Log4CXX User
Subject: Re: Segmentation fault log4cxx 0.10.0 on app exit (
RH Linux)

Do you have any of the network appenders or possibly the
AsyncAppender
configured? I'm guessing this is the same thread shutdown
issues I
reported on Windows in this thread:

http://www.nabble.com/A-few-problems-to-report-to1
7013024.html

The tip should be a bit better, but you might get a delay on
shutdown.

On Thu, May 29, 2008 at 3:15 PM, GregN <grshoreyahoo.com> wrote:
>
> Segmentation fault on app exit.
>
> log4cxx, apr-1.2.12 and apr-util-1.2.12 had been build
from tar file.
>
> gcc -v
> Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
> Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared
--enable-threads=posix
> --disable-checking --with-system-zlib
--enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-java-awt=gtk
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)
>
> $ uname -a
> Linux gredhat4 2.6.9-11.EL #1 Fri May 20 18:17:57 EDT
2005 i686 i686
i386
> GNU/Linux
>
>
> Test app successfully writes one line in log file with
code:
> int main() {
>   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
>    LoggerPtr LogManager::cplusLoggerPtr =
Logger::getLogger("API");
>    LOG4CXX_INFO(cplusLoggerPtr ,
"test_info");
>    return 0;
> }
>
>
> C++ [C/C++ Local Application]
>        gdb/mi (5/29/08 2:31 PM) (Suspended)
>                Thread [1] (Suspended: Signal 'SIGSEGV'
received.
Description:
> Segmentation fault.)
>                        8 apr_atomic_dec32()
atomic/unix/apr_atomic.c:310 0xb7d1efba
>                        7
log4cxx::helpers::ObjectImpl::releaseRef()
>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp:44
> 0xb7e36da0
>                        6 log4cxx::Logger::releaseRef()
>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
> 0xb7e20c5d
>                        5 ~ObjectPtrT()
/usr/local/include/log4cxx/helpers/objectptr.h:100
> 0x080550e3
>                        4 __tcf_1() /home/..project
specific...
>                        3 exit()  0x004ce467
>                        2 __libc_start_main() 
0x004b8e2d
>                        1 _start()  0x080545ad
>
> Any suggestion is welcome...
>
> Thanks,
> Gregory
>
> --
> View this message in context:
http://www.nabble.com/Segmentation-fault
-log4cxx-0.10.0-on-app-exit-%28-
RH-Linux%29-tp17543738p17543738.html
> Sent from the Log4cxx - Users mailing list archive at
Nabble.com.
>
>



-- 
Dale King

Only ConsoleAppender and RollingFileAppender are used.


Dale King-2 wrote:
> 
> Do you have any of the network appenders or possibly
the AsyncAppender
> configured? I'm guessing this is the same thread
shutdown issues I
> reported on Windows in this thread:
> 
> http://www.nabble.com/A-few-problems-to-report-to1
7013024.html
> 
> The tip should be a bit better, but you might get a
delay on shutdown.
> 
> On Thu, May 29, 2008 at 3:15 PM, GregN <grshoreyahoo.com> wrote:
>>
>> Segmentation fault on app exit.
>>
>> log4cxx, apr-1.2.12 and apr-util-1.2.12 had been
build from tar file.
>>
>> gcc -v
>> Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
>> Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man
>> --infodir=/usr/share/info --enable-shared
--enable-threads=posix
>> --disable-checking --with-system-zlib
--enable-__cxa_atexit
>> --disable-libunwind-exceptions
--enable-java-awt=gtk
>> --host=i386-redhat-linux
>> Thread model: posix
>> gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)
>>
>> $ uname -a
>> Linux gredhat4 2.6.9-11.EL #1 Fri May 20 18:17:57
EDT 2005 i686 i686 i386
>> GNU/Linux
>>
>>
>> Test app successfully writes one line in log file
with code:
>> int main() {
>>   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
>>    LoggerPtr LogManager::cplusLoggerPtr =
Logger::getLogger("API");
>>    LOG4CXX_INFO(cplusLoggerPtr ,
"test_info");
>>    return 0;
>> }
>>
>>
>> C++ [C/C++ Local Application]
>>        gdb/mi (5/29/08 2:31 PM) (Suspended)
>>                Thread [1] (Suspended: Signal
'SIGSEGV' received.
>> Description:
>> Segmentation fault.)
>>                        8 apr_atomic_dec32()
atomic/unix/apr_atomic.c:310
>> 0xb7d1efba
>>                        7
log4cxx::helpers::ObjectImpl::releaseRef()
>>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp:44
>> 0xb7e36da0
>>                        6
log4cxx::Logger::releaseRef()
>>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
>> 0xb7e20c5d
>>                        5 ~ObjectPtrT()
>> /usr/local/include/log4cxx/helpers/objectptr.h:100
>> 0x080550e3
>>                        4 __tcf_1() /home/..project
specific...
>>                        3 exit()  0x004ce467
>>                        2 __libc_start_main() 
0x004b8e2d
>>                        1 _start()  0x080545ad
>>
>> Any suggestion is welcome...
>>
>> Thanks,
>> Gregory
>>
>> --
>> View this message in context:
>> http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17543738.html
>> Sent from the Log4cxx - Users mailing list archive
at Nabble.com.
>>
>>
> 
> 
> 
> -- 
> Dale King
> 
> 

-- 
View this message in context: http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17558876.html
Sent from the Log4cxx - Users mailing list archive at
Nabble.com.

Omayre,

I can't find version 1.2.2 on http://apr.apache.
org/download.cgi
The 1.2.12 is the latest there.

Thanks,
Gregory


Omayre Zahid wrote:
> 
> I'm not sure how much this helps, but try to use
version 1.2.2. If I
> recall
> correctly, using the latest version of APR and APR-UTIL
gave me issues.
> 
> Regards,
> Omayre
> 
> On Thu, May 29, 2008 at 5:18 PM, Unnikrishnan Udinoor
> <uudinoorbrocade.com>
> wrote:
> 
>> I am facing similar issue with Solaris.
>> The following link explains my issue.
>>
>> http://mail-archives.apache.org/mod_mbox
/logging-log4cxx-user/200804.mbo
>> x/%3cEB4C465FC146B54DAADF4C8C0637BC6202BA6C6DHQ-EXCH-4.corp.brocade.com<http://mail-archives.apache.org/mod_mbox/logging-log4cx
x-user/200804.mbox/%3cEB4C465FC146B54DAADF4C8C0637BC6202BA6C
6DHQ-EXCH-4.corp.brocade.com>
>> %3e
>>
>> Couldn't really get out of this yet.
>>
>> Regards
>> Unni
>> -----Original Message-----
>> From: Dale King [mailto:dalewkinggmail.com]
>> Sent: Thursday, May 29, 2008 2:06 PM
>> To: Log4CXX User
>> Subject: Re: Segmentation fault log4cxx 0.10.0 on
app exit ( RH Linux)
>>
>> Do you have any of the network appenders or
possibly the AsyncAppender
>> configured? I'm guessing this is the same thread
shutdown issues I
>> reported on Windows in this thread:
>>
>> http://www.nabble.com/A-few-problems-to-report-to1
7013024.html
>>
>> The tip should be a bit better, but you might get a
delay on shutdown.
>>
>> On Thu, May 29, 2008 at 3:15 PM, GregN
<grshoreyahoo.com> wrote:
>> >
>> > Segmentation fault on app exit.
>> >
>> > log4cxx, apr-1.2.12 and apr-util-1.2.12 had
been build from tar file.
>> >
>> > gcc -v
>> > Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
>> > Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man
>> > --infodir=/usr/share/info --enable-shared
--enable-threads=posix
>> > --disable-checking --with-system-zlib
--enable-__cxa_atexit
>> > --disable-libunwind-exceptions
--enable-java-awt=gtk
>> > --host=i386-redhat-linux
>> > Thread model: posix
>> > gcc version 3.4.3 20050227 (Red Hat
3.4.3-22.1)
>> >
>> > $ uname -a
>> > Linux gredhat4 2.6.9-11.EL #1 Fri May 20
18:17:57 EDT 2005 i686 i686
>> i386
>> > GNU/Linux
>> >
>> >
>> > Test app successfully writes one line in log
file with code:
>> > int main() {
>> >   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
>> >    LoggerPtr LogManager::cplusLoggerPtr =
Logger::getLogger("API");
>> >    LOG4CXX_INFO(cplusLoggerPtr ,
"test_info");
>> >    return 0;
>> > }
>> >
>> >
>> > C++ [C/C++ Local Application]
>> >        gdb/mi (5/29/08 2:31 PM) (Suspended)
>> >                Thread [1] (Suspended: Signal
'SIGSEGV' received.
>> Description:
>> > Segmentation fault.)
>> >                        8 apr_atomic_dec32()
>> atomic/unix/apr_atomic.c:310 0xb7d1efba
>> >                        7
log4cxx::helpers::ObjectImpl::releaseRef()
>> >
>>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp:44
>> > 0xb7e36da0
>> >                        6
log4cxx::Logger::releaseRef()
>> >
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
>> > 0xb7e20c5d
>> >                        5 ~ObjectPtrT()
>> /usr/local/include/log4cxx/helpers/objectptr.h:100
>> > 0x080550e3
>> >                        4 __tcf_1()
/home/..project specific...
>> >                        3 exit()  0x004ce467
>> >                        2 __libc_start_main() 
0x004b8e2d
>> >                        1 _start()  0x080545ad
>> >
>> > Any suggestion is welcome...
>> >
>> > Thanks,
>> > Gregory
>> >
>> > --
>> > View this message in context:
>> http://www.nabble.com/Segmentation-fault
-log4cxx-0.10.0-on-app-exit-%28-
>> RH-Linux%29-tp17543738p17543738.html<
http://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-a
pp-exit-%28-RH-Linux%29-tp17543738p17543738.html>
>> > Sent from the Log4cxx - Users mailing list
archive at Nabble.com.
>> >
>> >
>>
>>
>>
>> --
>> Dale King
>>
> 
> 

-- 
View this message in context: http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17559288.html
Sent from the Log4cxx - Users mailing list archive at
Nabble.com.

Thanks, Omayre.
I'll try it.


Omayre Zahid wrote:
> 
> Greg,
> 
> That's true, apache archived that version. It can now
be found here:
> http://archive.ap
ache.org/dist/apr/
> 
> Regards,
> Omayre
> 
> On Fri, May 30, 2008 at 9:47 AM, GregN <grshoreyahoo.com> wrote:
> 
>>
>> Omayre,
>>
>> I can't find version 1.2.2 on http://apr.apache.
org/download.cgi
>> The 1.2.12 is the latest there.
>>
>> Thanks,
>> Gregory
>>
>>
>> Omayre Zahid wrote:
>> >
>> > I'm not sure how much this helps, but try to
use version 1.2.2. If I
>> > recall
>> > correctly, using the latest version of APR and
APR-UTIL gave me issues.
>> >
>> > Regards,
>> > Omayre
>> >
>> > On Thu, May 29, 2008 at 5:18 PM, Unnikrishnan
Udinoor
>> > <uudinoorbrocade.com>
>> > wrote:
>> >
>> >> I am facing similar issue with Solaris.
>> >> The following link explains my issue.
>> >>
>> >>
>> http://mail-archives.apache.org/mod_mbox
/logging-log4cxx-user/200804.mbo
>> >> x/%
>> 3cEB4C465FC146B54DAADF4C8C0637BC6202BA6C6DHQ-EXCH-4.corp.brocade.com<
>> http://mail-archives.apache.org/mod_mbox/logging-log4cx
x-user/200804.mbox/%3cEB4C465FC146B54DAADF4C8C0637BC6202BA6C
6DHQ-EXCH-4.corp.brocade.com
>> >
>> >> %3e
>> >>
>> >> Couldn't really get out of this yet.
>> >>
>> >> Regards
>> >> Unni
>> >> -----Original Message-----
>> >> From: Dale King [mailto:dalewkinggmail.com]
>> >> Sent: Thursday, May 29, 2008 2:06 PM
>> >> To: Log4CXX User
>> >> Subject: Re: Segmentation fault log4cxx
0.10.0 on app exit ( RH Linux)
>> >>
>> >> Do you have any of the network appenders
or possibly the AsyncAppender
>> >> configured? I'm guessing this is the same
thread shutdown issues I
>> >> reported on Windows in this thread:
>> >>
>> >> http://www.nabble.com/A-few-problems-to-report-to1
7013024.html
>> >>
>> >> The tip should be a bit better, but you
might get a delay on shutdown.
>> >>
>> >> On Thu, May 29, 2008 at 3:15 PM, GregN
<grshoreyahoo.com> wrote:
>> >> >
>> >> > Segmentation fault on app exit.
>> >> >
>> >> > log4cxx, apr-1.2.12 and
apr-util-1.2.12 had been build from tar
>> file.
>> >> >
>> >> > gcc -v
>> >> > Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
>> >> > Configured with: ../configure
--prefix=/usr --mandir=/usr/share/man
>> >> > --infodir=/usr/share/info
--enable-shared --enable-threads=posix
>> >> > --disable-checking --with-system-zlib
--enable-__cxa_atexit
>> >> > --disable-libunwind-exceptions
--enable-java-awt=gtk
>> >> > --host=i386-redhat-linux
>> >> > Thread model: posix
>> >> > gcc version 3.4.3 20050227 (Red Hat
3.4.3-22.1)
>> >> >
>> >> > $ uname -a
>> >> > Linux gredhat4 2.6.9-11.EL #1 Fri May
20 18:17:57 EDT 2005 i686 i686
>> >> i386
>> >> > GNU/Linux
>> >> >
>> >> >
>> >> > Test app successfully writes one line
in log file with code:
>> >> > int main() {
>> >> >   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
>> >> >    LoggerPtr
LogManager::cplusLoggerPtr =
Logger::getLogger("API");
>> >> >    LOG4CXX_INFO(cplusLoggerPtr ,
"test_info");
>> >> >    return 0;
>> >> > }
>> >> >
>> >> >
>> >> > C++ [C/C++ Local Application]
>> >> >        gdb/mi (5/29/08 2:31 PM)
(Suspended)
>> >> >                Thread [1] (Suspended:
Signal 'SIGSEGV' received.
>> >> Description:
>> >> > Segmentation fault.)
>> >> >                        8
apr_atomic_dec32()
>> >> atomic/unix/apr_atomic.c:310 0xb7d1efba
>> >> >                        7
log4cxx::helpers::ObjectImpl::releaseRef()
>> >> >
>> >>
>>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp:44
>> >> > 0xb7e36da0
>> >> >                        6
log4cxx::Logger::releaseRef()
>> >> >
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
>> >> > 0xb7e20c5d
>> >> >                        5
~ObjectPtrT()
>> >>
/usr/local/include/log4cxx/helpers/objectptr.h:100
>> >> > 0x080550e3
>> >> >                        4 __tcf_1()
/home/..project specific...
>> >> >                        3 exit() 
0x004ce467
>> >> >                        2
__libc_start_main()  0x004b8e2d
>> >> >                        1 _start() 
0x080545ad
>> >> >
>> >> > Any suggestion is welcome...
>> >> >
>> >> > Thanks,
>> >> > Gregory
>> >> >
>> >> > --
>> >> > View this message in context:
>> >>
>> http://www.nabble.com/Segmentation-fault
-log4cxx-0.10.0-on-app-exit-%28-
>> >> RH-Linux%29-tp17543738p17543738.html<
>> http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17543738.html
>> >
>> >> > Sent from the Log4cxx - Users mailing
list archive at Nabble.com.
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Dale King
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17559288.html
>> Sent from the Log4cxx - Users mailing list archive
at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17560330.html
Sent from the Log4cxx - Users mailing list archive at
Nabble.com.

Omayre,

It is the same fault with version 1.2.2...

I tryed the same test with log4cpp and it works fine.
If I can't get the way to resolve the issue I will use it.

Thanks,
Gregory




GregN wrote:
> 
> Thanks, Omayre.
> I'll try it.
> 
> 
> Omayre Zahid wrote:
>> 
>> Greg,
>> 
>> That's true, apache archived that version. It can
now be found here:
>> http://archive.ap
ache.org/dist/apr/
>> 
>> Regards,
>> Omayre
>> 
>> On Fri, May 30, 2008 at 9:47 AM, GregN
<grshoreyahoo.com> wrote:
>> 
>>>
>>> Omayre,
>>>
>>> I can't find version 1.2.2 on http://apr.apache.
org/download.cgi
>>> The 1.2.12 is the latest there.
>>>
>>> Thanks,
>>> Gregory
>>>
>>>
>>> Omayre Zahid wrote:
>>> >
>>> > I'm not sure how much this helps, but try
to use version 1.2.2. If I
>>> > recall
>>> > correctly, using the latest version of APR
and APR-UTIL gave me
>>> issues.
>>> >
>>> > Regards,
>>> > Omayre
>>> >
>>> > On Thu, May 29, 2008 at 5:18 PM,
Unnikrishnan Udinoor
>>> > <uudinoorbrocade.com>
>>> > wrote:
>>> >
>>> >> I am facing similar issue with
Solaris.
>>> >> The following link explains my issue.
>>> >>
>>> >>
>>> http://mail-archives.apache.org/mod_mbox
/logging-log4cxx-user/200804.mbo
>>> >> x/%
>>> 3cEB4C465FC146B54DAADF4C8C0637BC6202BA6C6DHQ-EXCH-4.corp.brocade.com<
>>> http://mail-archives.apache.org/mod_mbox/logging-log4cx
x-user/200804.mbox/%3cEB4C465FC146B54DAADF4C8C0637BC6202BA6C
6DHQ-EXCH-4.corp.brocade.com
>>> >
>>> >> %3e
>>> >>
>>> >> Couldn't really get out of this yet.
>>> >>
>>> >> Regards
>>> >> Unni
>>> >> -----Original Message-----
>>> >> From: Dale King [mailto:dalewkinggmail.com]
>>> >> Sent: Thursday, May 29, 2008 2:06 PM
>>> >> To: Log4CXX User
>>> >> Subject: Re: Segmentation fault
log4cxx 0.10.0 on app exit ( RH
>>> Linux)
>>> >>
>>> >> Do you have any of the network
appenders or possibly the
>>> AsyncAppender
>>> >> configured? I'm guessing this is the
same thread shutdown issues I
>>> >> reported on Windows in this thread:
>>> >>
>>> >> http://www.nabble.com/A-few-problems-to-report-to1
7013024.html
>>> >>
>>> >> The tip should be a bit better, but
you might get a delay on
>>> shutdown.
>>> >>
>>> >> On Thu, May 29, 2008 at 3:15 PM, GregN
<grshoreyahoo.com> wrote:
>>> >> >
>>> >> > Segmentation fault on app exit.
>>> >> >
>>> >> > log4cxx, apr-1.2.12 and
apr-util-1.2.12 had been build from tar
>>> file.
>>> >> >
>>> >> > gcc -v
>>> >> > Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
>>> >> > Configured with: ../configure
--prefix=/usr --mandir=/usr/share/man
>>> >> > --infodir=/usr/share/info
--enable-shared --enable-threads=posix
>>> >> > --disable-checking
--with-system-zlib --enable-__cxa_atexit
>>> >> > --disable-libunwind-exceptions
--enable-java-awt=gtk
>>> >> > --host=i386-redhat-linux
>>> >> > Thread model: posix
>>> >> > gcc version 3.4.3 20050227 (Red
Hat 3.4.3-22.1)
>>> >> >
>>> >> > $ uname -a
>>> >> > Linux gredhat4 2.6.9-11.EL #1 Fri
May 20 18:17:57 EDT 2005 i686
>>> i686
>>> >> i386
>>> >> > GNU/Linux
>>> >> >
>>> >> >
>>> >> > Test app successfully writes one
line in log file with code:
>>> >> > int main() {
>>> >> >   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
>>> >> >    LoggerPtr
LogManager::cplusLoggerPtr =
Logger::getLogger("API");
>>> >> >    LOG4CXX_INFO(cplusLoggerPtr ,
"test_info");
>>> >> >    return 0;
>>> >> > }
>>> >> >
>>> >> >
>>> >> > C++ [C/C++ Local Application]
>>> >> >        gdb/mi (5/29/08 2:31 PM)
(Suspended)
>>> >> >                Thread [1]
(Suspended: Signal 'SIGSEGV' received.
>>> >> Description:
>>> >> > Segmentation fault.)
>>> >> >                        8
apr_atomic_dec32()
>>> >> atomic/unix/apr_atomic.c:310
0xb7d1efba
>>> >> >                        7
log4cxx::helpers::ObjectImpl::releaseRef()
>>> >> >
>>> >>
>>>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp:44
>>> >> > 0xb7e36da0
>>> >> >                        6
log4cxx::Logger::releaseRef()
>>> >> >
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
>>> >> > 0xb7e20c5d
>>> >> >                        5
~ObjectPtrT()
>>> >>
/usr/local/include/log4cxx/helpers/objectptr.h:100
>>> >> > 0x080550e3
>>> >> >                        4
__tcf_1() /home/..project specific...
>>> >> >                        3 exit() 
0x004ce467
>>> >> >                        2
__libc_start_main()  0x004b8e2d
>>> >> >                        1 _start()
 0x080545ad
>>> >> >
>>> >> > Any suggestion is welcome...
>>> >> >
>>> >> > Thanks,
>>> >> > Gregory
>>> >> >
>>> >> > --
>>> >> > View this message in context:
>>> >>
>>> http://www.nabble.com/Segmentation-fault
-log4cxx-0.10.0-on-app-exit-%28-
>>> >>
RH-Linux%29-tp17543738p17543738.html<
>>> http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17543738.html
>>> >
>>> >> > Sent from the Log4cxx - Users
mailing list archive at Nabble.com.
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Dale King
>>> >>
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17559288.html
>>> Sent from the Log4cxx - Users mailing list
archive at Nabble.com.
>>>
>>>
>> 
>> 
> 
> 

-- 
View this message in context: http
://www.nabble.com/Segmentation-fault-log4cxx-0.10.0-on-app-e
xit-%28-RH-Linux%29-tp17543738p17565158.html
Sent from the Log4cxx - Users mailing list archive at
Nabble.com.

On May 29, 2008, at 2:15 PM, GregN wrote:

>
> Segmentation fault on app exit.
>
> log4cxx, apr-1.2.12 and apr-util-1.2.12 had been build
from tar file.
>
> gcc -v
> Reading specs from
/usr/lib/gcc/i386-redhat-linux/3.4.3/specs
> Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared
--enable-threads=posix
> --disable-checking --with-system-zlib
--enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-java-awt=gtk
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)
>
> $ uname -a
> Linux gredhat4 2.6.9-11.EL #1 Fri May 20 18:17:57 EDT
2005 i686 i686  
> i386
> GNU/Linux
>
>
> Test app successfully writes one line in log file with
code:
> int main() {
>   
PropertyConfigurator::configure(LOG_PROPERTIES_FILE_LOCATION
);
>    LoggerPtr LogManager::cplusLoggerPtr =
Logger::getLogger("API");
>    LOG4CXX_INFO(cplusLoggerPtr ,
"test_info");
>    return 0;
> }
>
>
> C++ [C/C++ Local Application]	
> 	gdb/mi (5/29/08 2:31 PM) (Suspended)	
> 		Thread [1] (Suspended: Signal 'SIGSEGV' received.
Description:
> Segmentation fault.)	
> 			8 apr_atomic_dec32() atomic/unix/apr_atomic.c:310
0xb7d1efba	
> 			7 log4cxx::helpers::ObjectImpl::releaseRef()
>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/object
impl.cpp: 
> 44
> 0xb7e36da0	
> 			6 log4cxx::Logger::releaseRef()
>
/home/grn/Projects/apache-log4cxx-0.10.0/src/main/cpp/logger
.cpp:62
> 0xb7e20c5d	
> 			5 ~ObjectPtrT()
/usr/local/include/log4cxx/helpers/objectptr.h:100
> 0x080550e3	
> 			4 __tcf_1() /home/..project specific...	
> 			3 exit()  0x004ce467	
> 			2 __libc_start_main()  0x004b8e2d	
> 			1 _start()  0x080545ad
>
> Any suggestion is welcome...
>
> Thanks,
> Gregory	
>

APR goes to great length to try to use a platform provided
atomic  
increment and decrement operation to implement
apr_atomic_dec32 and  
apr_atomic_inc32, but contains a fallback implementation
that uses APR  
mutexes to guard the operation.  The stack trace suggests
that the  
fallback mechanism was used after APR was terminated  
APRInitializer::~APRInitializer.  Only the fallback
implementation is  
susceptible to crashing if APR is terminated prematurely.

It is unclear why was the fallback implementation of
apr_atomic_dec32  
compiled when building APR.  From your platform description,
it  
appears that the inline assembler implementations near the
top of  
atomic/unix/apr_atomic.c should have been compiled.

You could probably avoid the Segmentation fault by
changing:

LoggerPtr LogManager::cplusLoggerPtr =
Logger::getLogger("API");

to:

LoggerPtr
LogManager::cplusLoggerPtr(Logger::getLogger("API"
));

The problem is that the default constructor for LoggerPtr
does not  
initialize APR and so when things are destructed, APR gets
terminated  
before the LoggerPtr is released.  Using the one operation
constructor  
causes APR to be initialized before the LoggerPtr is
constructed and  
so the destruction occurs in the proper order.