[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: heimdal 0.6.2 coredumps
James F. Hranicky wrote:
> This looks like an OpenLDAP bug
Agreed, you should file an OpenLDAP ITS report.
>
> if (l->lm_chain == NULL) {
> if ((l->lm_msgtype == LDAP_RES_SEARCH_ENTRY) ||
> (l->lm_msgtype == LDAP_RES_SEARCH_REFERENCE) ||
> (l->lm_msgtype == LDAP_RES_INTERMEDIATE)) {
> /* do not advance lm_chain_tail in this case */
> l->lm_chain = new;
> } else {
> /*FIXME: ldap_msgfree( l );*/
> l = new;
> l->lm_chain_tail = new;
> }
> } else {
> => if ((l->lm_chain_tail->lm_chain->lm_msgtype
> == LDAP_RES_SEARCH_ENTRY) ||
> (l->lm_chain_tail->lm_chain->lm_msgtype
> == LDAP_RES_SEARCH_REFERENCE) ||
> (l->lm_chain_tail->lm_chain->lm_msgtype
> == LDAP_RES_INTERMEDIATE)) {
> l->lm_chain_tail->lm_chain->lm_chain = new;
> l->lm_chain_tail = l->lm_chain_tail->lm_chain;
> } else {
> /*FIXME: ldap_msgfree( l->lm_chain_tail->lm_chain );*/
> l->lm_chain_tail->lm_chain = new;
> }
> }
>
> The struct l looks like this:
>
> 3: *l = {lm_msgid = 2, lm_msgtype = 100, lm_ber = 0x8070920, lm_chain = 0x8071630,
> lm_chain_tail = 0x0, lm_next = 0x0, lm_time = 0}
>
> Oops. It looks like l->lm_chain is set, but l->lm_chain_tail isn't. I think
> this should probably be reported to the OpenLDAP list. I'll do so unless
> someone thinks this is a heimdal bug.
--
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
http://www.symas.com http://highlandsun.com/hyc
Symas: Premier OpenSource Development and Support