Closed
Bug 10554
Opened 25 years ago
Closed 25 years ago
nsRegistry::GetString reimplements strdup()
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
WONTFIX
M11
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().
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M9
Assignee | ||
Updated•25 years ago
|
Severity: normal → minor
Target Milestone: M9 → M11
Assignee | ||
Comment 1•25 years ago
|
||
This strdup is using PR_Malloc. The has to free this using PR_Free. Changing
this to nsCRT will mean changing all callers.
Minor.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 2•25 years ago
|
||
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?
You need to log in
before you can comment on or make changes to this bug.
Description
•