Closed
Bug 37662
Opened 25 years ago
Closed 24 years ago
assertion viewing source on a newsgroup message
Categories
(MailNews Core :: Networking: NNTP, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
Future
People
(Reporter: alecf, Assigned: sspitzer)
Details
I'm getting an assertion when I view source on a newsgroup message, in
nsNntpUrl::GetNewsgroupName:
(gdb) frame 1
#1 0x41420908 in nsNntpUrl::GetNewsgroupName (this=0xbdebba0, aNewsgroupName=
0xbffff448)
at nsNntpUrl.cpp:385
385 NS_ASSERTION(m_newsgroupName, "null ptr");
(gdb) list
380
381 NS_IMETHODIMP nsNntpUrl::GetNewsgroupName(char ** aNewsgroupName)
382 {
383 if (!aNewsgroupName) return NS_ERROR_NULL_POINTER;
384
385 NS_ASSERTION(m_newsgroupName, "null ptr");
386 if (!m_newsgroupName) return NS_ERROR_FAILURE;
387
388 *aNewsgroupName = PL_strdup(m_newsgroupName);
389 if (!aNewsgroupName) {
Reporter | ||
Comment 1•25 years ago
|
||
I should add that I then get this:
JavaScript error:
line 0: uncaught exception: [Exception... "Component does not have requested
interface" code: "-2147467262" nsresult: "0x80004002 (NS_NOINTERFACE)"
location: "<unknown>"]
and then the view source window comes up fine.
Assignee | ||
Comment 2•25 years ago
|
||
I have another bug that relates to this, see
http://bugzilla.mozilla.org/show_bug.cgi?id=36647
Status: NEW → ASSIGNED
Comment 4•25 years ago
|
||
moving to future milestone since view source is still working fine.
Target Milestone: M17 → Future
Mass moving all NEWS bugs from esther to myself.
QA Contact: lchiang → stephend
Comment 6•24 years ago
|
||
Worksforme. Alec, can you please verify that this worksforyou now?
Thanks
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•24 years ago
|
Status: RESOLVED → VERIFIED
Comment 7•24 years ago
|
||
cannot test the assert but I no longer get javascript error when viewing source
of newsgroup messages...
build 20011018
Updated•20 years ago
|
Product: MailNews → Core
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
•