In my case, it turns out the problem is related to bad mail headers in
my mail spool file. I built thunderbird locally on my machine so I could
better debug the crash:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff39f5034 in nsMovemailService::GetNewMail (this=0x7fffd9f4ed40,
aMsgWindow=<optimized out>,
aUrlListener=<optimized out>, aMsgFolder=<optimized out>,
movemailServer=<optimized out>, aURL=<optimized out>)
at
/home/drewm/projects/thunderbird/thunderbird-15.0.1+build1/./mailnews/local/src/nsMovemailService.cpp:465
465 outputStream->Write(buffer.get(), buffer.Length(), &bytesWritten);
(gdb) print buffer
$1 = {<nsFixedCString> = {<nsCString> = {<nsACString_internal> = {
mData = 0x7fffffffafb8 "rom drewm Fri Oct 12 08:55:12 2012\n", mLength
= 36,
mFlags = 65553}, <No data fields>}, mFixedCapacity = 63,
mFixedBuf = 0x7fffffffafb8 "rom drewm Fri Oct 12 08:55:12 2012\n"},
mStorage = "rom drewm Fri Oct 12 08:55:12
2012\n\000\177\000\000@\r\245\323\377\177\000\000\224I\244\026\000\000\000\000\224I\244\026\000\000\000"}
(gdb) print outputStream
$2 = {<nsCOMPtr_base> = {mRawPtr = 0x0}, <No data fields>}
(gdb)
The mStorage line begins with "rom" instead of "from" and it appears
that outputStream is null in this case.
If I repair my mail spool and correct this header then Thunderbird
starts without crashing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046531
Title:
Thunderbird 15.0 crash with local Movemail account
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1046531/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
