abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: /usr/lib/thunderbird-3.1/thunderbird-bin --sm-config-prefix /thunderbird-bin-DCdOcL/ --sm-client-id 106f726361000124343613200000023350009 --screen 0 component: thunderbird crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib/thunderbird-3.1/thunderbird-bin kernel: 2.6.35.6-48.fc14.i686.PAE package: thunderbird-3.1.6-1.fc14 rating: 4 reason: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) How to reproduce: System was running overnight. Came in in the morning and thunderbird had crashed. time: 1288858765 uid: 1744 comment ----- Appears to be here in nsSSLThread::requestRecvMsgPeek: memcpy(buf, si->mThreadData->mSSLRemainingReadResultData, return_amount); (gdb) print si->mThreadData->mSSLRemainingReadResultData $2 = 0x0 gdb) print *si->mThreadData $4 = {mSSLState = nsSSLSocketThreadData::ssl_idle, mPRErrorCode = 0, mSSLDataBuffer = 0xa3368000 "6206 OK Idle completed.\r\nt NonJunk) UID 735)\r\n6205 OK Fetch completed.\r\n6201 OK Status completed.\r\ng\">photran</a>\r\n<a class=\"moz-txt-link-freetext\" href=\"https://dev.eclipse.org/mailman/li"..., mSSLDataBufferAllocatedSize = 4096, mSSLRequestedTransferAmount = 4096, mSSLRemainingReadResultData = 0x0, mSSLResultRemainingBytes = 0, mReplacedSSLFileDesc = 0x0, mOneBytePendingFromEarlierWrite = 0, mThePendingByte = 86 'V', mOriginalRequestedTransferAmount = 0} (gdb) print amount $5 = 1 (gdb) print si->mThreadData->mSSLResultRemainingBytes $6 = 0 For some reason I think memcpy(source, 0, 0) can segfault these days....
Created attachment 457810 [details] File: backtrace
*** This bug has been marked as a duplicate of bug 641422 ***