Closed
Bug 220288
Opened 22 years ago
Closed 20 years ago
News crashes when a message is selected from a newsgroup with character '&' (ampersand) in name
Categories
(MailNews Core :: Networking: NNTP, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: filipmiletic, Assigned: sspitzer)
References
()
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
An experimental news server at news://news.elitesecurity.org has a conference
named: elitesecurity.programiranje.python-&-zope. Selecting any message from it
causes News to crash. I suspect that it might be because of the ampersand in the
name.
Last few lines of the reproduction, running as: mozilla --debug
[New Thread 13326 (LWP 754)]
[New Thread 14351 (LWP 755)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 673)]
0x41407e80 in NSGetModule () from /usr/local/mozilla/components/libmsgnews.so
(gdb)
Reproducible: Always
Steps to Reproduce:
1. Subscribe to news://news.elitesecurity.org:119
2. Subscribe to elitesecurity.programiranje.python-&-zope
3. Select any message for viewing.
Actual Results:
All Mozilla windows close. If run from a terminal, user sees no SIGSEGV message.
If run in --debug mode, user sees the message about the SIGSEGV, as quoted above.
Expected Results:
Mozilla should not crash.
Theme is 'old style' Mozilla.
Comment 1•22 years ago
|
||
WFM using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20030925
Comment 2•22 years ago
|
||
do you still crash using 1.6b ?
Updated•21 years ago
|
Product: MailNews → Core
Comment 3•20 years ago
|
||
No response from reporter for several months, marking WFM.
Reporter: Please reopen this bug, if you could reproduce with recent build and
could provide Talkback incident ID.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•