abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/lib/thunderbird-3.0/thunderbird-bin component: thunderbird executable: /usr/lib/thunderbird-3.0/thunderbird-bin kernel: 2.6.31.6-166.fc12.i686 package: thunderbird-3.0-4.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 380944 [details] File: backtrace
#3 <signal handler called> No symbol table info available. #4 0x01068e97 in nsSSLThread::requestRecvMsgPeek (si=<value optimized out>, buf=<value optimized out>, amount=1, flags=<value optimized out>, timeout=<value optimized out>) at /usr/include/bits/string3.h:52 return_amount = 1 threadLock = {<nsAutoLockBase> = {<No data fields>}, mLock = 0xafeda220, mLocked = 1} realSSLFD = <value optimized out> #5 0x01078cfd in PSMRecv (fd=<value optimized out>, buf=<value optimized out>, amount=<value optimized out>, flags=<value optimized out>, timeout=<value optimized out>) at /usr/src/debug/thunderbird-3.0/comm-1.9.1/mozilla/security/manager/ssl/src/nsNSSIOLayer.cpp:2029 locker = {<No data fields>} socketInfo = 0xafd8b880 #6 0x0653045e in PR_Recv (fd=<value optimized out>, buf=<value optimized out>, amount=<value optimized out>, flags=<value optimized out>, timeout=<value optimized out>) at ../../../mozilla/nsprpub/pr/src/io/priometh.c:220 No locals. #7 0x01f19eaf in nsSocketTransport::IsAlive (this=<value optimized out>, result=<value optimized out>) at /usr/src/debug/thunderbird-3.0/comm-1.9.1/mozilla/netwerk/base/src/nsSocketTransport2.cpp:1808 fd = 0xb0e3f2e0 c = 1 '\001' rval = <value optimized out> #8 0x013104cc in nsImapProtocol::CanHandleUrl (this=<value optimized out>, aImapUrl=<value optimized out>, aCanRunUrl=<value optimized out>, hasToWait=<value optimized out>) at /usr/src/debug/thunderbird-3.0/comm-1.9.1/mailnews/imap/src/nsImapProtocol.cpp:2074 isAlive = <value optimized out> rv = 0 isBusy = 0 isInboxConnection = 0 curSelectedUrlFolderName = {<nsFixedCString> = {<nsCString> = {<nsACString_internal> = {mData = 0x1015aa40 <Address 0x1015aa40 out of bounds>, mLength = 293874, mFlags = 19805057}, <No data fields>}, mFixedCapacity = 22378292, mFixedBuf = 0x4b3b54a1 <Address 0x4b3b54a1 out of bounds>}, mStorage = "8I\t\000\064wU\001\000\031\336\264\254\332\343\277\001\256.\001 L\274\257\000\240\242\257\000K\266g\000\000\000\000c1\034\001\064wU\001h\211\035\020\362{\004\000\024L\274\257\000\000\000\000\035\000\000"} imapState = <value optimized out> msgUrl = {<nsCOMPtr_base> = {mRawPtr = 0xaeee6f48}, <No data fields>} server = {<nsCOMPtr_base> = {mRawPtr = 0x15e2da2}, <No data fields>} mon = {<nsAutoLockBase> = {<No data fields>}, mLockObject = 0xafbc4c00, mLockCount = 1} inSelectedState = <value optimized out> actionForProposedUrl = <value optimized out> pendingUrlFolderName = {<nsFixedCString> = {<nsCString> = {<nsACString_internal> = {mData = 0xbfe3d9fc ",\332\343\277\203x\033\001\200e\350\256HR>\001\214\332\343\277HR>\001 \240\242\257\300\372^\001\346l\255", mLength = 0, mFlags = 2934861640}, <No data fields>}, mFixedCapacity = 106296656, mFixedBuf = 0xbfe3da8c "\035"}, mStorage = ",\332\343\277\203x\033\001\200e\350\256HR>\001\214\332\343\277HR>\001 \240\242\257\300\372^\001\346l\255\000;\351T\006L\332\343\277\000\000\000\000L\332\343\277\241\063.\001\000\031\336\264HR>\001"} -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. First of all, could we get output of the command rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin* *thunderbird* Please also install thunderbird-debuginfo (debuginfo-install is from yum-utils package). debuginfo-install thunderbird Then run firefox inside the gdb debugger. Please do the following: $ thunderbird -g stuff will appear. ignore this until you get the gdb command prompt, then do: (gdb) run Now, thunderbird should start up. Use it and reproduce the crash. When thunderbird crashes, you should be back to the gdb prompt. Now do: (gdb) thread apply all backtrace More screens of stuff will occur. Copy all of this part to your editor of choice, such as gedit, and save it as an uncompressed file and attach it to this bug report. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
*** This bug has been marked as a duplicate of bug 573602 ***