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/[EMAIL PROTECTED]
%3e

Couldn't really get out of this yet.

Regards
Unni
-----Original Message-----
From: Dale King [mailto:[EMAIL PROTECTED] 
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-to17013024.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 <[EMAIL PROTECTED]> 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/objectimpl.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

Reply via email to