2 Feb
2006
2 Feb
'06
5:14 p.m.
When using the following in a module initialization function:
MAKE_CONSTANT_SHARED_STRING(a[i], "somestring");
the resulting string has a refcount of 2. if you then use
free_string(a[i]);
in the corresponding exit function, dmalloc reports a leak. when doing the same, but just on a pointer, rather than an array, dmalloc doesn't seem to care. Is this expected behavior? Is it an issue that the items aren't actually freed by free_string (because of the extra ref)? I'd imagine that it's probably not critical in this case, as we're talking about a module.
Bill