On Tue, 23 Oct 2007 01:00:08 +0200 Tomasz Sterna <[EMAIL PROTECTED]> wrote:
> Dnia 22-10-2007, Pn o godzinie 15:03 -0400, Ryan Pugatch pisze: > > Yes, I did a make clean. Backtrace just has a bunch of stuff like: > > > > #0 0x00000030 in ?? () > > #1 0x082456a0 in ?? () > > #2 0x082456a0 in ?? () > > #3 0x00c44158 in main_arena () from /lib/libc.so.6 The last output in sm's log was: Mon Oct 22 09:34:38 2007 storage_db.c:161 serialising key time Segmentation fault Try setting a breakpoint there (inside gdb type ``break storage_db.c:161'') and then step from there on (whith ``next''). Maybe you catch the faulting call this way. > > Looks like your glibc is stripped off symbols. > Check if your distribution delivers -debug version of glibc. Hm, but even if glibc is stripped, there has to be one function in this back trace that's inside sm and thus should be printed. Also, there are 256 lines in the bt. How do you get so many nested function calls? AFAIK jabberd2 doesn't use any recursion ... Regards, harry _______________________________________________ Jabberd2 mailing list [email protected] http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
