Description of problem: I get a Gecko crash for nearly all of the messages in my folders. Version-Release number of selected component (if applicable): [robin@preston ~]$ uname -a Linux preston 2.6.24.3-50.fc8 #1 SMP Thu Mar 20 14:47:10 EDT 2008 i686 athlon i386 GNU/Linux [robin@preston ~]$ thunderbird -v Thunderbird 2.0.0.12, Copyright (c) 1998-2008 mozilla.org How reproducible: Open thunderbird, select a message (same thing happens with either the view pane or by double clicking a message to open it in a separate window) I have saved a couple of bug reports. The attached one was produced while trying to open the automatically generated message sent to me by my bugzilla registration... I can easily generate more if required.
Created attachment 299642 [details] bug report
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. Please install thunderbid-debuginfo (debuginfo-install is from yum-utils package). debuginfo-install thunderbid Then run thunderbid with a parameter -g. That will start thunderbid running inside of gdb debugger. Then use command run and do whatever you did to make thunderbid crash. When it happens, you should go back to the gdb and run (gdb) thread apply all backtrace This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
I am sorry for not explaining completely -- the backtrace you have sent is generated for the new generation of the debugging application used by Mozilla, which unfortunately a) we have no tools to analyze the output of, b) produces outputs totally irrelevant for the builds we made in Fedora. Later we have switched it off, but for many people we used to generate these huge but unfortunately for our purposes totally useless reports. So, I have asked to regenerate your backtrace using the good old gdb. Could you do it for us, please? Thank you very much.
Reporter, 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.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.