> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Mcdaid, Paul (GAL:IE319) > Sent: Friday, November 28, 2008 10:45 AM > To: [email protected] > Subject: [sipX-dev] sipxsupervisor crash in 3.11.8-014115. > > I've seen the following crash of sipxsupervisor in 014115: > Has anyone else seen this? Can anyone shed any light on it? > > Here's the stack trace: > > *** glibc detected *** /usr/local/sipx/bin/sipxsupervisor: > double free or corruption (out): 0xb25011 60 *** ======= > Backtrace: ========= /lib/libc.so.6[0x872a96] > /lib/libc.so.6(cfree+0x90)[0x875fb0] > /lib/libcrypto.so.6(CRYPTO_free+0x3a)[0x3e948a] > /lib/libcrypto.so.6[0x43e858] > /lib/libcrypto.so.6(ERR_get_state+0x10f)[0x43f47f] > /lib/libcrypto.so.6(ERR_clear_error+0x1b)[0x43fafb] > /lib/libssl.so.6(ssl23_connect+0x5d)[0x6f579d] > /lib/libssl.so.6(SSL_connect+0x2a)[0x70100a]
did you check before you posted :-) It must be something we have done recently... since three of us are seeing it today, and nobody complained before. We have many more threads doing xmlrpc now. I think we have exposed an existing bug (failure to do some ssl locking). Carolyn _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
