Tomasz Sterna wrote:
Dnia 2008-09-05, pią o godzinie 13:56 +0400, Proskurin Kirill pisze:
Im try to do trace via ktrace/kdump freebsd tool.
Unfortunately the syscall trace is not really usefull for crash
debugging.
I need the stack back trace to see what happened.
Please install gdb and run sm under gdb control, then after crash issue
the 'bt' gdb command to get stack back trace.
Alternatively connect gdb to a running sm instance.
Alternatively set your system to dump cores (ulimit -c unlimited) and
get a 'bt' post mortem.
See http://fedoraproject.org/wiki/StackTraces or
http://live.gnome.org/GettingTraces/Details for more information.
These documents explains the procedure better than I could ever explain
it on the ML.
Im start jabberd2 without sm.
%/usr/local/etc/rc.d/jabberd start
Starting jabberd.
%sockstat
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
jabber c2s 1832 4 tcp4 127.0.0.1:62473 127.0.0.1:5347
jabber c2s 1832 5 tcp4 *:5222 *:*
jabber router 1831 4 tcp4 *:5347 *:*
jabber router 1831 5 tcp4 127.0.0.1:5347 127.0.0.1:62473
%gdb /usr/local/bin/sm
GNU gdb 6.1.1 [FreeBSD]
This GDB was configured as "i386-marcel-freebsd"...
(gdb) run -c /usr/local/etc/jabberd/sm.xml
Starting program: /usr/local/bin/sm -c /usr/local/etc/jabberd/sm.xml
*im reproduce crash*
/libexec/ld-elf.so.1: /usr/local/lib/jabberd/storage_db.so: Undefined
symbol "ser_string_set"
Program exited with code 01.
(gdb)
Then im type:
(gdb) thread apply all bt
(gdb) bt
No stack.
(gdb)
Something wrong with db4?..
Im allready try to rebuild it and jabberd2...
Use another version of db? Which?
--
Best regards,
Proskurin Kirill
--
To unsubscribe send a mail to [EMAIL PROTECTED]
