Open Bug 447994 Opened 16 years ago Updated 2 years ago

<nsImapService.cpp> has unused assignments

Categories

(MailNews Core :: Networking: IMAP, defect)

defect

Tracking

(Not tracked)

People

(Reporter: sgautherie, Unassigned)

References

Details

<http://mxr.mozilla.org/comm-central/source/mailnews/imap/src/nsImapService.cpp>
{{
635     rv = url->SetSpec(urlSpec);
636     
637     rv = aImapUrl->SetImapAction(actionToUse /* nsIImapUrl::nsImapMsgFetch */);
}}

Remove |rv = | at line 635, or check its value.

***

Same with
{{
1018   rv = url->SetSpec(urlSpec);
...
1063   rv = aImapUrl->SetImapAction(aImapAction);
}}

and
{{
3027     rv = imapUrl->SetImapAction(nsIImapUrl::nsImapUserDefinedFetchAttribute);
...
3032     rv = SetImapUrlSink(anImapFolder, imapUrl);
}}

... Basically, check the whole file.
(In reply to comment #1)
> Do the following crashes relate to this bug?

"Thunderbird 3.0b1pre Crash Report [@ nsImapService::CreateStartOfImapUrl(nsACString_internal const&, nsIImapUrl**, nsIMsgFolder*, nsIUrlListener*, nsACString_internal&, unsigned short&) ]"

Doubtful, unless it would be prevented by checking these return values.
For the time being, you should rather search/file a new bug.
Product: Core → MailNews Core
The setSpec cases should be covered in bug 186724.

There are many spots where rv doesn't seem to be checked after assignment.

David Bienvenu, are you still working on this? Is this just a matter of adding the checks everywhere (with a bit of sense)?
Depends on: 186724
(In reply to :aceman from comment #3)
> The setSpec cases should be covered in bug 186724.
> 
> There are many spots where rv doesn't seem to be checked after assignment.
> 
> David Bienvenu, are you still working on this? Is this just a matter of
> adding the checks everywhere (with a bit of sense)?
and sometimes removing the rv assignment, but yes, this is simple, and I'm not working on it.
Assignee: dbienvenu → nobody
And how can I decide where to remove the assignment?
Severity: trivial → S4
You need to log in before you can comment on or make changes to this bug.