Questions about iter check in profile_iterator()

Shawn M Emery shawn.emery at
Tue Jan 13 01:45:52 EST 2015

On 01/12/15 08:40 PM, Greg Hudson wrote:
> On 01/12/2015 07:06 PM, Neng Xue wrote:
>> So my question is that do we use the
>> profile_iterator() in the wrong way or there should be an iter check in
>> the profile_iterator()? Thanks.
> The loop condition should be "state != NULL" rather than "code == 0".
> profile_iterator_create returns 0 and sets *iter_p to NULL on the last
> iteration.

We may want to change other functions like krb5_425_conv_principal if 
this is the intended conditional.

> On 01/12/2015 08:13 PM, Will Fiveash wrote:
>> So in the profile_iterator call to profile_node_iterator() the
>> &iter->idata arg is iter_p for profile_node_iterator?  Seems odd to me.
> I don't see what is odd about that.  iter->idata holds the node iterator
> state.
> _______________________________________________
> krbdev mailing list             krbdev at

More information about the krbdev mailing list