[Date Prev][Date Next]
Re: FW: syncrepl.c uses strndup() (ITS#2481)
I changed strndup() to ch_strdup().
Also changed are strdup()s in config.c to ch_strdup().
Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
(phone) 914-945-3979 (fax) 914-945-4425 TL: 862-3979
"Howard Chu" <firstname.lastname@example.org>@OpenLDAP.org on 05/02/2003 08:07:17 AM
Sent by: owner-openldap-devel@OpenLDAP.org
Subject: FW: syncrepl.c uses strndup() (ITS#2481)
[mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
Full_Name: Hallvard B. Furuseth
Submission from: (NULL) (22.214.171.124)
syncrepl.c uses the function strndup(), which does not exist.
ber_strndup(), ber_strndup_x(), LBER_STRNDUP(), LDAP_STRNDUP(),
LDAP_STRNDUPX() and SLAP_STRNDUP() exist, I don't know which
one is supposed to be used.
The LDAP_STR* macros are for libldap's internal use. Likewise the LBER_STR*
macros are only for use within liblber.
Of the func() vs func_x() variant, the plain func just calls func_x with a
NULL context to get the regular global malloc, and is provided for backward
compatibility. I've been using the _x functions directly in places, to
the extra function call, but you really only need it if you want the
allocation to come from the thread-local memory context. In this particular
case, the strndup's appear to be for values that must come from regular
malloc, so using a NULL memory context would be correct. I guess Jong
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support