"moo" should never crash; it just prints a bunch of stuff and exits.
It really shouldn't crash sporadically.  And in fact it doesn't.  Based
on core dumps, the crash is clearly happening due to something in
log4cxx.  Here thread 2 is the one that actually crashed.

Thread 2 (Thread 13246):
#0  0xb75f21ca in ?? () from /usr/lib/libsigc-2.0.so.0
#1  0xb75f2827 in sigc::signal_base::~signal_base() () from 
/usr/lib/libsigc-2.0.so.0
#2  0xb616f828 in __cxa_finalize (d=0xb75ef644) at cxa_finalize.c:56
#3  0xb75586a4 in __do_global_dtors_aux () from /usr/lib/libcwidget.so.3
#4  0xb75cfbe0 in _fini () from /usr/lib/libcwidget.so.3
#5  0xb78d6bab in _dl_fini () at dl-fini.c:248
#6  0xb616f481 in __run_exit_handlers (status=0, listp=0xb6283324, 
run_list_atexit=true) at exit.c:78
#7  0xb616f4df in *__GI_exit (status=0) at exit.c:100
#8  0xb6156b5d in __libc_start_main (main=0x8073bd0 <main>, argc=3, 
ubp_av=0xbf894824, init=0x8365920 <__libc_csu_init>, fini=0x8365910 
<__libc_csu_fini>, rtld_fini=0xb78d69b0 <_dl_fini>, 
    stack_end=0xbf89481c) at libc-start.c:254
#9  0x080729d1 in _start ()

Thread 1 (Thread 13247):
#0  0xb5f9b092 in ?? () from /usr/lib/libapr-1.so.0
#1  0xb5f9ba90 in apr_pool_create_ex () from /usr/lib/libapr-1.so.0
#2  0xb77088a8 in log4cxx::helpers::Pool::Pool() () from 
/usr/lib/liblog4cxx.so.10
#3  0xb7732652 in log4cxx::helpers::ThreadLocal::ThreadLocal() () from 
/usr/lib/liblog4cxx.so.10
#4  0xb7731e22 in log4cxx::helpers::Thread::getThreadLocal() () from 
/usr/lib/liblog4cxx.so.10
#5  0xb7732072 in log4cxx::helpers::Thread::launcher(apr_thread_t*, void*) () 
from /usr/lib/liblog4cxx.so.10
#6  0xb5fa9985 in ?? () from /usr/lib/libapr-1.so.0
#7  0xb63a0585 in start_thread (arg=0xb58e8b70) at pthread_create.c:300
#8  0xb620f29e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

  My guess is that log4cxx isn't destroying its background threads
early enough.  The -vvvvvvv probably has some effect on timing, and I
bet the i386/amd64 difference is also a timing thing.

  Since this is a bug that could affect other parts of the program,
I'm promoting it to "normal" priority.

  Daniel



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to