> Sorry for the stupid question, but how can I get a stack trace? gdb?
This is the stacktrace with GDB and my program compiled with "gcc -g"
after a program crash just after calling dkim_init() libcall:
dkimcour: mod dkim_verify: DEBUG: _filter_mail(): 59: setting up opendkim
library
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff1aa8910 (LWP 9537)]
0x00007ffff7484f45 in raise () from /lib/libc.so.6
(gdb) backtrace
#0 0x00007ffff7484f45 in raise () from /lib/libc.so.6
#1 0x00007ffff7487d80 in abort () from /lib/libc.so.6
#2 0x00007ffff74ba54d in ?? () from /lib/libc.so.6
#3 0x00007ffff74c3d16 in ?? () from /lib/libc.so.6
#4 0x00007ffff74c89bc in free () from /lib/libc.so.6
#5 0x00007ffff6ed9aad in CRYPTO_free () from /usr/lib/libcrypto.so.0.9.8
#6 0x00007ffff6edc952 in OBJ_NAME_add () from /usr/lib/libcrypto.so.0.9.8
#7 0x00007ffff6f43e85 in OpenSSL_add_all_ciphers () from
/usr/lib/libcrypto.so.0.9.8
#8 0x00007ffff6f43e2e in OPENSSL_add_all_algorithms_noconf () from
/usr/lib/libcrypto.so.0.9.8
#9 0x00007ffff7bd5103 in dkim_init (caller_mallocf=0x2535,
caller_freef=0x2541) at dkim.c:3816
#10 0x00007ffff62b38f5 in _filter_mail (sessionid=39) at dkim_verify.c:145
#11 0x0000000000407746 in do_module_filter (sessionid=39) at modules.c:141
#12 0x00000000004098f4 in hit_for_unanimity () at threads.c:140
#13 0x0000000000409672 in handle_requests_loop (data=0x60e784) at
threads.c:66
#14 0x00007ffff77ad73a in start_thread () from /lib/libpthread.so.0
#15 0x00007ffff751e69d in clone () from /lib/libc.so.6
#16 0x0000000000000000 in ?? ()
(gdb)
HTH
With a mutex this is no more happening.
Thank you! Ciao, Dino.
--
Dino Ciuffetti
Linux System Administrator and Architect
TuxWeb S.r.l. - http://www.tuxweb.it/
Received on Fri Apr 30 2010 - 14:13:59 PST