Closed
Bug 329161
Opened 19 years ago
Closed 13 years ago
seamonkey crashes when sorting messages by subject [@ strxfrm - nsCollationUnix::AllocateRawSortKey]
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: yevg, Assigned: smontagu)
Details
(Keywords: crash)
Crash Data
Attachments
(2 files, 1 obsolete file)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0
see summary, reproduces always under debian sarge.
Reproducible: Always
Steps to Reproduce:
1.open mail&news
2.go to inbox (or view-sort)
3.sort by subject
Actual Results:
crash
Expected Results:
good sorting by subject
Comment 1•19 years ago
|
||
any talkback incident id?
Reporter: if you're using a debian build, then you should complain to debian, or rebuild w/ --enable-debug --disable-optimize --disable-strip.
if you're using a mozilla.org, please be sure to select talkback from the installer.
Reporter | ||
Comment 3•19 years ago
|
||
(In reply to comment #2)
> Reporter: if you're using a debian build, then you should complain to debian,
> or rebuild w/ --enable-debug --disable-optimize --disable-strip.
This is seamonkey linux build from mozilla.org (which is gtk2 english).
> if you're using a mozilla.org, please be sure to select talkback from the
> installer.
There is no talkback available in installer options. I've installed everything, except javascript debugger. Seamonkey shows 'Segmentation fault' immediately after sorting messages by subject. No talkback window appears.
Comment 4•19 years ago
|
||
SeaMonkey branch builds don't have talkback. You'll need to try a trunk build:
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/
Version: unspecified → 1.8 Branch
Reporter | ||
Comment 5•19 years ago
|
||
this log was created by seamonkey compiled from source tarball of official 1.0 release with --enable-debug --disable-optimize --disable-strip on debian sarge 3.1r1
Comment 6•19 years ago
|
||
looks like an i18n function is crashing. In particular, my guess is some collation key generator's AllocateRawSortKey function.
Is it just your inbox that has this problem, or do other folders? If it's just your inbox, it could be one particular message that's causing the problem, and you could figure out which message through a binary search (i.e., copy half the inbox to another folder; try to sort that folder; if it crashes, copy half of that folder to another folder, etc...)
note the last line of your log file:
Type 'gdb /usr/local/lib/seamonkey-1.0/seamonkey-bin 1155' to attach your debugger to this thread.
the next time you produce this, please follow the advice given by the output in your terminal window.
from gdb, type |where| and then provide that stack trace. thanks :)
Reporter | ||
Comment 8•19 years ago
|
||
this is gdb logfile
Reporter | ||
Comment 9•19 years ago
|
||
this is seamonkey crashlog connected with supplied gdb log
Attachment #214473 -
Attachment is obsolete: true
Comment 10•19 years ago
|
||
cool, in gdb, try going to frame 7 and doing info locals, list, p varname and such. see if you can figure out what is being past to the function at frame 6.
Assignee: mail → smontagu
Component: MailNews: Main Mail Window → Internationalization
Keywords: crash
Product: Mozilla Application Suite → Core
QA Contact: amyy
Summary: seamonkey crashes when sorting messages by subject → seamonkey crashes when sorting messages by subject [@ strxfrm - nsCollationUnix::AllocateRawSortKey]
Comment 11•19 years ago
|
||
erm, i suppose i meant passed not past. sorry :(
http://www.mozilla.org/unix/debugging-faq.html may be of help
Reporter | ||
Comment 12•19 years ago
|
||
I've downloaded latest trunk seamonkey 1.5a and generated talkback incident. ID: TB16129721K
Comment 13•19 years ago
|
||
the good news is that it matches the gdb output.
the bad news is that using gdb is going to get you a lot further than talkback will at this point :(.
Reporter | ||
Comment 14•19 years ago
|
||
After numerous experiments the problem was solved with replacing belocs-locales with locales package from Debian distribution.
Comment 15•16 years ago
|
||
Yevgeny: Would this bug be a WORKSFORME resolution, since you took care of it with replace the locales package? If not, can you reproduce it with Firefox 3.5?
Updated•16 years ago
|
QA Contact: amyy → i18n
Updated•14 years ago
|
Crash Signature: [@ strxfrm - nsCollationUnix::AllocateRawSortKey]
Comment 16•13 years ago
|
||
invalid per comment 14
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•