[389-devel] plugin problem using slapi_entry_attr_find

[Deas, Jim]

On further review it appears that the line in question will crash Dirsrv on some request from PAM or even 389-Console but not when searching groups via ldapsearch
Should there be a statement that determines what type of query triggered the preop_result so I know if it’s proper  to look for attributes?


From: 389-devel-bounces at lists.fedoraproject.org [mailto:389-devel-bounces at lists.fedoraproject.org] On Behalf Of Rich Megginson
Sent: Thursday, January 16, 2014 11:29 AM
To: 389 Directory server developer discussion.
Subject: Re: [389-devel] plugin problem using slapi_entry_attr_find

On 01/16/2014 11:39 AM, Deas, Jim wrote:
My bet, a rookie mistake. Am I forgetting to init a pointer etc???
Adding  the line surrounded by ******  in this routine makes dirsrv unstable and crashes it after a few queries.




/* Registered preop_result routine */
int gnest_preop_results( Slapi_PBlock *pb){
                Slapi_Entry *e;
                Slapi_Attr  **a;
This should be Slapi_Attr *a;


If (slapi_pblock_get( pb, SLAPI_SEARCH_ATTRS, &e) !=0 )return (-1);

/*****************This line makes the server unstable and crashes it after one or two queries ********************/
If(slapi_entry_attr_find(e, “memberUid”,&a) == 0) slapi_log_error(SLAPI_LOG_PLUGIN, “gnest preop”,”memberUid  found in record);
/******************************************************************************************************/


Return (0);
}

JD





--

389-devel mailing list

389-devel at lists.fedoraproject.org<mailto:389-devel at lists.fedoraproject.org>

https://admin.fedoraproject.org/mailman/listinfo/389-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-devel/attachments/20140116/1d2c280b/attachment.html>