[jdev] jabberd2s10 crashes on FC4 with muc-conf/jcr
driver at enjine.net
driver at enjine.net
Sun Jan 1 17:19:11 CST 2006
> see if you can get a core dump, then load it up in gdb for a full
> backtrace with filenames and line numbers.
>
> On 12/31/05, driver at enjine.net <driver at enjine.net> wrote:
>> yeah -- i've got it built with debugging on. i also have the logs but
>> there's nothing out of the ordinary in them. i build jabberd2, applied
>> the
>> flash patch, then compiled jcr/mu-conference and attached it. it was
>> running fine for a few hours -- then it started crashing after a few
>> clients were connected, and now it wont even start up.
>>
>>
>>
>> > unfortunatly that Backtrace isn't going to help anyone. Is there any
>> > chance you could rebuild jabberd with debugging information?
>> >
>> > I'm not exactly sure how to enable debugging on jabberd2, but it can't
>> > be that different from http://www.amule.org/wiki/index.php/Backtraces
>> >
>> > On 12/31/05, driver at enjine.net <driver at enjine.net> wrote:
>> >> anyone have this problem..
>> >> it runs fine for a while but once i have 3 or 4 different clients
>> >> (xiff/tkabber/trillian/gush) all connected it shits the bed..
>> >>
>> >> WTF???!?!
>> >>
>> >> here's the backtrace --
>> >>
>> >> *** glibc detected *** /usr/local/bin/c2s: double free or corruption
>> >> (!prev): 0x0a0151e8 ***
>> >> ======= Backtrace: ========> /lib/libc.so.6[0x213424]
>> >> /lib/libc.so.6(__libc_free+0x77)[0x21395f]
>> >> /usr/local/bin/c2s[0x80576b4]
>> >> /usr/local/bin/c2s[0x80536c4]
>> >> /usr/local/bin/c2s[0x804ecd7]
>> >> /usr/local/bin/c2s[0x807baeb]
>> >> /usr/local/bin/c2s[0x804dc23]
>> >> /usr/local/bin/c2s[0x8057a6c]
>> >> /usr/local/bin/c2s[0x8053a24]
>> >> /usr/local/bin/c2s[0x8050140]
>> >> /usr/local/bin/c2s[0x8057a6c]
>> >>
>>
>>
>
>
> --
> - Norman Rasmussen
> - Email: norman at rasmussen.co.za
> - Home page: http://norman.rasmussen.co.za/
>
i don't think i know hoe to get a core dump.
and i also don't knoe what you mean when you say 'load it up in gdb for a
full backtrace with filenames and line numbers' sorry.
More information about the JDev
mailing list