[389-devel] plugin problem using slapi_entry_attr_find

2014-01-16 Thread Deas, Jim
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;

Re: [389-devel] plugin problem using slapi_entry_attr_find

2014-01-16 Thread Deas, Jim
for attributes? From: 389-devel-boun...@lists.fedoraproject.org [mailto:389-devel-boun...@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

Re: [389-devel] plugin problem using slapi_entry_attr_find

2014-01-16 Thread Rich Megginson
:* 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

Re: [389-devel] plugin problem using slapi_entry_attr_find

2014-01-16 Thread Nathan Kinder
PM *To:* 389 Directory server developer discussion. *Subject:* Re: [389-devel] plugin problem using slapi_entry_attr_find Another bug in your code. The argument for SLAPI_SEARCH_ATTRS should be the address of a char **.e.g. { char **attrs; int ii = 0

Re: [389-devel] plugin problem using slapi_entry_attr_find

2014-01-16 Thread Rich Megginson
...@lists.fedoraproject.org] On Behalf Of Nathan Kinder Sent: Thursday, January 16, 2014 3:35 PM To: 389 Directory server developer discussion. Subject: Re: [389-devel] plugin problem using slapi_entry_attr_find On 01/16/2014 03:14 PM, Deas, Jim wrote: Rich, Thanks. I actually did have the address of operator