Closed Bug 10554 Opened 25 years ago Closed 25 years ago

nsRegistry::GetString reimplements strdup()

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: bruce, Assigned: dp)

Details

Very interesting wheel you have there. It looks a lot like the wheel that most of us know as PL_strdup() or nsCRT::strdup() however. This is referring to the lines after if (err == REGERR_OK) after getting NR_RegGetEntryString().
Status: NEW → ASSIGNED
Target Milestone: M9
Severity: normal → minor
Target Milestone: M9 → M11
This strdup is using PR_Malloc. The has to free this using PR_Free. Changing this to nsCRT will mean changing all callers. Minor.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
scc was (is still?) working on fixing allocation and deallocation of all char* data in the product. It stands to reason that any callers in this case would need to be corrected anyway. Is this not so? Should this be re-opened?
Component: XPCOM Registry → XPCOM
QA Contact: dp → xpcom
You need to log in before you can comment on or make changes to this bug.