Reminder. If openssl-dev subscribers want RT users to "hear" them, reply explicitly to [EMAIL PROTECTED]
David Schwartz wrote: >> [EMAIL PROTECTED] ([EMAIL PROTECTED]) terminated by signal BUS (invalid >> address alignment) >> 0xffffffff7d24fab8: t_delete+0x00f8: stx %o0, [%g4 + 16] >> current thread: [EMAIL PROTECTED] >> [1] t_delete(0x11c303480, 0x0, 0xffffffff7f268340, 0x2000, >> 0x2190, 0x1004e4290), at 0xffffffff7d24fab8 >> [2] _malloc_unlocked(0x80, 0x0, 0x0, 0x11ad552e0, 0x11ad552e0, >> 0x0), at 0xffffffff7d24f068 >> [3] malloc(0x80, 0xffffffff7e502458, 0xffffffff7e5014f0, >> 0xf68, 0x24fd00, 0xc00), at 0xffffffff7d24ee94 >> =>[4] CRYPTO_malloc(num = ???, file = ???, line = ???) >> (optimized), at 0xffffffff7e2b2274 (line ~304) in "mem.c" > > OpenSSL just called 'malloc'. This trace is of the victim, not the > culprit. Try running under purify or valgrind to find the culprit. Most like scenario is that some allocated buffer was overrun and corrupted memory manager's structure. Sun Workshop dbx also offers means for tracking memory errors, see 'help rtc'. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
