Hello everyone,

After running just fine for months, Jabberd2's router somehow started
to crash within the sasl_gsasl.c file.  I ran the router under gdb
with debug output turned on (-D).  I'm not quite sure what else I can
provide, other than this is Gentoo's Jabberd2 version 2.1.21 using
PostgreSQL 8.2.6, and fails regardless of my chosen CFLAGS.  What
could be the cause of the segfaults?

- Neil

========== OUTPUT ==========

sx (io.c:234) decoded read data (71 bytes): <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
>>> NAD OP nad_new: 0xc832be10
>>> NAD OP nad_add_namespace: 0xc832be10
>>> NAD OP nad_find_scoped_namespace: 0xc832be10
>>> NAD OP nad_add_namespace: 0xc832be10
>>> NAD OP nad_find_scoped_namespace: 0xc832be10
>>> NAD OP nad_append_elem: 0xc832be10
>>> NAD OP nad_append_attr: 0xc832be10
>>> NAD OP nad_print: 0xc832be10
sx (io.c:89) completed nad: <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
sx (chain.c:119) calling nad read chain
>>> NAD OP nad_find_attr: 0xc832be10
sx (sasl_gsasl.c:291) auth request from client (mechanism=DIGEST-MD5)
sx (sasl_gsasl.c:334) sasl context initialised for 9

Program received signal SIGSEGV, Segmentation fault.
0x00002d46e72f1715 in ?? ()
(gdb) where
#0  0x00002d46e72f1715 in ?? ()
#1  0x0000000000000001 in ?? ()
#2  0x000004f5c81db5ad in ?? ()
#3  0x0000000000000008 in ?? ()
#4  0x000004f5c832bf10 in ?? ()
#5  0x00000071ffffffff in ?? ()
#6  0x000004f500000000 in ?? ()
#7  0x0000000000000000 in ?? ()

-- 
To unsubscribe send a mail to [EMAIL PROTECTED]

Reply via email to